@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? -- Best regards, Alex Lourie Software Developer in Integration Red Hat ----- Original Message -----
From: "Alon Bar-Lev" <alonbl@redhat.com> To: "Karli Sjöberg" <Karli.Sjoberg@slu.se> Cc: users@ovirt.org Sent: Thursday, August 1, 2013 2:20:06 PM Subject: Re: [Users] Fedora upgrading from 3.1 to 3.2
----- Original Message -----
From: "Karli Sjöberg" <Karli.Sjoberg@slu.se> To: "Alon Bar-Lev" <alonbl@redhat.com> Cc: users@ovirt.org Sent: Thursday, August 1, 2013 12:50:11 PM Subject: Re: [Users] Fedora upgrading from 3.1 to 3.2
tor 2013-08-01 klockan 05:29 -0400 skrev Alon Bar-Lev:
----- Original Message -----
From: "Karli Sjöberg" <Karli.Sjoberg@slu.se<mailto:Karli.Sjoberg@slu.se>> To: "Alon Bar-Lev" <alonbl@redhat.com<mailto:alonbl@redhat.com>> Cc: "Alex Lourie" <alourie@redhat.com<mailto:alourie@redhat.com>>, users@ovirt.org<mailto:users@ovirt.org>, "Eli Mesika" <emesika@redhat.com<mailto:emesika@redhat.com>> Sent: Thursday, August 1, 2013 12:24:57 PM Subject: Re: [Users] Fedora upgrading from 3.1 to 3.2
Ah, my bad, I botched that when doing the patch for "engine-setup" and hadn´t made an original copy so I did "yum erase" and "yum install" again to get back the original file, and yum was nice enough to erase and install blank files for me, heh. Now I´m back again and once more updated those option values in the database, but I´m still not able to log in. The log is attached.
The engine.log you sent is too short for typical log...
Can we start from scratch? What exactly are you doing? What sequence?
OK, to make a long story a little shorter. I´m trying to go from oVirt-3.1 to oVirt-3.2 on Fedora, so this is what I have done so far:
(After Fedora is up to 18, and the old engine is up and running, I was able to log in) - Erase all of the 3.1-packages - Install the new 3.2-packages - Have to go about the dbase upgrade like this: # psql -U postgres engine $ ALTER FUNCTION uuid_generate_v1() OWNER TO engine; $ \q Or the upgrade won´t work. After that it´s possible to: # cd /usr/share/ovirt-engine/dbscripts # ./upgrade.sh -s localhost -p 5432 -u engine -d engine (lots of output) # engine-cleanup --dont-drop-db
- Had to make modifications to "/usr/bin/engine-setup" for the setup to complete OK. @@ -1142,8 +1142,8 @@ # Run db backup utils.backupDB( db=basedefs.DB_NAME, - backup_file=dbBackupFile, - env=utils.getPgPassEnv(), + backupFile=dbBackupFile, + #env=utils.getPgPassEnv(), user=getDbUser(), host=getDbHostName(), port=getDbPort(),
# engine-setup # systemctl stop ovirt-engine # psql -U engine engine $ update vdc_options set option_value = '/etc/pki/ovirt-engine/keys/engine.p12' where option_name = 'keystoreUrl'; $ update vdc_options set option_value = '/etc/pki/ovirt-engine/certs/engine.cer' where option_name = 'CertificateFileName'; $ update vdc_options set option_value = '/etc/pki/ovirt-engine/.truststore' where option_name = 'TruststoreUrl'; $ \q # cat /dev/null > /var/log/ovirt-engine/engine.log # systemctl restart ovirt-engine; tail -f /var/log/ovirt-engine/engine.log | tee /tmp/engine_start.log
That is the log you now have seen.
And why don't you use engine-upgrade?
I think that in this process you probably remove your existing keys from /etc/pki/ovirt-engine
Thanks, Alon
--
Med Vänliga Hälsningar ------------------------------------------------------------------------------- Karli Sjöberg Swedish University of Agricultural Sciences Box 7079 (Visiting Address Kronåsvägen 8) S-750 07 Uppsala, Sweden Phone: +46-(0)18-67 15 66 karli.sjoberg@slu.se<mailto:karli.sjoberg@adm.slu.se>
_______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users