----- Original Message -----
From: "Trey Dockendorf" <treydock@gmail.com> To: "users" <users@ovirt.org> Sent: Wednesday, February 12, 2014 8:19:25 PM Subject: [Users] Downgrading to 3.3.3 after 3.4.0 beta 2 testing
The update to 3.4.0 beta2 was very smooth. My 3.3.3 setup was very basic so my testing was not extremely extensive, but I wanted to make sure I could still override NFS mount options (I could) to ensure use of RDMA.
Now I'd like to downgrade, but that was not as simple as I'd hoped. I could not find any definitive docs on the subject so pieced together the steps.
# Backup 3.3.3 $ engine-backup --mode=backup --scope=all --file=engine-20140211-1457.tar.bz2 --log=engine-backup.log
# Enabled the 3.4.0 repo per release notes $ yum update ovirt-engine-setup $ engine-setup
# I tested 3.4.0 and wanted to "downgrade".
$ engine-backup --mode=restore --scope=all --file=engine-20140211-1457.tar.bz2 --log=engine-backup.log FATAL: Engine service is active - can not restore backup
$ /etc/init.d/ovirt-engine stop
$ engine-backup --mode=restore --scope=all --file=engine-20140211-1457.tar.bz2 --log=engine-backup.log Restoring... FATAL: Backup version '3.3' doesn't match installed version
# Disabled the 3.4.0 repo $ yum downgrade ovirt-engine-setup-3.3.3-2.el6 Loaded plugins: downloadonly, fastestmirror, security, versionlock Setting up Downgrade Process Loading mirror speeds from cached hostfile Resolving Dependencies --> Running transaction check ---> Package ovirt-engine-setup.noarch 0:3.3.3-2.el6 will be a downgrade ---> Package ovirt-engine-setup.noarch 0:3.4.0-0.7.beta2.el6 will be erased --> Finished Dependency Resolution Error: Package: ovirt-engine-3.4.0-0.7.beta2.el6.noarch (@ovirt-3.4.0-prerelease) Requires: ovirt-engine-setup >= 3.4.0-0.7.beta2.el6 Removing: ovirt-engine-setup-3.4.0-0.7.beta2.el6.noarch (@ovirt-3.4.0-prerelease) ovirt-engine-setup = 3.4.0-0.7.beta2.el6 Downgraded By: ovirt-engine-setup-3.3.3-2.el6.noarch (ovirt-3.3.3) ovirt-engine-setup = 3.3.3-2.el6 Available: ovirt-engine-setup-3.3.0-4.el6.noarch (ovirt-stable) ovirt-engine-setup = 3.3.0-4.el6 Available: ovirt-engine-setup-3.3.0.1-1.el6.noarch (ovirt-stable) ovirt-engine-setup = 3.3.0.1-1.el6 Available: ovirt-engine-setup-3.3.1-1.el6.noarch (ovirt-stable) ovirt-engine-setup = 3.3.1-1.el6 Available: ovirt-engine-setup-3.3.1-2.el6.noarch (ovirt-stable) ovirt-engine-setup = 3.3.1-2.el6 Available: ovirt-engine-setup-3.3.2-1.el6.noarch (ovirt-stable) ovirt-engine-setup = 3.3.2-1.el6 You could try using --skip-broken to work around the problem You could try running: rpm -Va --nofiles --nodigest
# Re-enabled the 3.4.0 repo $ yum downgrade ovirt-engine-setup-3.3.3-2.el6 Loaded plugins: downloadonly, fastestmirror, security, versionlock Setting up Downgrade Process Loading mirror speeds from cached hostfile ovirt-3.3.3
| 2.9 kB 00:00 ovirt-3.4.0-prerelease
| 3.4 kB 00:00 ovirt-stable
| 2.9 kB 00:00 Resolving Dependencies --> Running transaction check ---> Package ovirt-engine-setup.noarch 0:3.3.3-2.el6 will be a downgrade ---> Package ovirt-engine-setup.noarch 0:3.4.0-0.7.beta2.el6 will be erased --> Finished Dependency Resolution Error: Package: ovirt-engine-3.4.0-0.7.beta2.el6.noarch (@ovirt-3.4.0-prerelease) Requires: ovirt-engine-setup >= 3.4.0-0.7.beta2.el6 Removing: ovirt-engine-setup-3.4.0-0.7.beta2.el6.noarch (@ovirt-3.4.0-prerelease) ovirt-engine-setup = 3.4.0-0.7.beta2.el6 Downgraded By: ovirt-engine-setup-3.3.3-2.el6.noarch (ovirt-3.3.3) ovirt-engine-setup = 3.3.3-2.el6 Available: ovirt-engine-setup-3.3.0-4.el6.noarch (ovirt-stable) ovirt-engine-setup = 3.3.0-4.el6 Available: ovirt-engine-setup-3.3.0.1-1.el6.noarch (ovirt-stable) ovirt-engine-setup = 3.3.0.1-1.el6 Available: ovirt-engine-setup-3.3.1-1.el6.noarch (ovirt-stable) ovirt-engine-setup = 3.3.1-1.el6 Available: ovirt-engine-setup-3.3.1-2.el6.noarch (ovirt-stable) ovirt-engine-setup = 3.3.1-2.el6 Available: ovirt-engine-setup-3.3.2-1.el6.noarch (ovirt-stable) ovirt-engine-setup = 3.3.2-1.el6 Available: ovirt-engine-setup-3.4.0-0.5.beta1.el6.noarch (ovirt-3.4.0-prerelease) ovirt-engine-setup = 3.4.0-0.5.beta1.el6 You could try using --skip-broken to work around the problem You could try running: rpm -Va --nofiles --nodigest
# Disable 3.4.0 repo again $ yum remove ovirt-engine-setup ovirt-engine-setup-base $ yum install ovirt-engine-setup
$ engine-backup --mode=restore --scope=all --file=engine-20140211-1457.tar.bz2 --log=engine-backup.log Restoring... FATAL: Database is not empty
$ engine-cleanup $ engine-backup --mode=restore --scope=all --file=engine-20140211-1457.tar.bz2 --log=engine-backup.log Restoring... FATAL: Database is not empty
Attached are the two engine-cleanup logs from both attempts. The first (from 20140211) was answering "Yes" only to "remove Engine DB content". The second (from 20140212, today) was "Yes" to "remove all components".
Apparently engine-cleanup does not clean up everything. We tried to make it do that, and I am pretty certain it used to at some point... 1. You might want to open a bug about this. As you already posted, manually dropping and creating the database still works... 2. Adding infra@ - I think we should add a jenkins job to verify that engine-cleanup cleans up at least the database, perhaps other things. I am pretty certain it should be so for 3.3, didn't check 3.4 yet. Best regards, -- Didi