<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 TRANSITIONAL//EN">
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta name="GENERATOR" content="GtkHTML/4.4.4">
</head>
<body>
tor 2013-08-01 klockan 07:46 -0400 skrev Alex Lourie:
<blockquote type="CITE">
<pre>
@Alon
Upgrade from 3.1 to 3.2 doesn't work in upstream, that's why we are doing this.
@Karli - are you keeping the keys/certificates from the 3.1 installation?
</pre>
</blockquote>
<br>
That time, no I didn´t. By this time, I was rather fed up with Fedora so I started thinking outside the box a little. So I reinstalled Fedora 17, installed engine and reran engine-setup. After that I made a backup, then reinstalled to CentOS-6.4 and used dreyou´s
repo to regain oVirt-3.1. Then I ran engine-setup, shut the engine down, dropped the db, restored the previous db I had when it was Fedora and restored /etc/pki/ovirt-engine/certs, /keys, .keystore and .truststore. After a restart of httpd and ovirt-engine
I was able to log in to the 3.1-engine that was originally set up in Fedora. And since that worked alright, I proceeded with following dreyou´s excellent (because it´s tested) guide for upgrading from 3.1 to 3.2, and it worked!!! So the once Fedora/oVirt-3.1
engine is now a CentOS/oVirt-3.2 engine instead:)<br>
<br>
So as it turns out, the best way of upgrading from oVirt-3.1 on Fedora is...to switch to CentOS...<br>
<br>
I will rerun the procedure again from start, but this time with added Hosts, Storage, etc. to confirm.<br>
<br>
<table cellspacing="0" cellpadding="0" width="100%">
<tbody>
<tr>
<td>-- <br>
<br>
Med Vänliga Hälsningar<br>
-------------------------------------------------------------------------------<br>
Karli Sjöberg<br>
Swedish University of Agricultural Sciences<br>
Box 7079 (Visiting Address Kronåsvägen 8)<br>
S-750 07 Uppsala, Sweden<br>
Phone: +46-(0)18-67 15 66<br>
<a href="mailto:karli.sjoberg@adm.slu.se">karli.sjoberg@slu.se</a> </td>
</tr>
</tbody>
</table>
</body>
</html>