[Users] Downgrading to 3.3.3 after 3.4.0 beta 2 testing

[Trey Dockendorf]

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".

Thanks
- Trey
-------------- next part --------------
A non-text attachment was scrubbed...
Name: ovirt-engine-remove-20140211190029.log
Type: application/octet-stream
Size: 696607 bytes
Desc: not available
URL: <http://lists.ovirt.org/pipermail/users/attachments/20140212/ad1be4fc/attachment-0002.obj>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: ovirt-engine-remove-20140212120512.log
Type: application/octet-stream
Size: 174239 bytes
Desc: not available
URL: <http://lists.ovirt.org/pipermail/users/attachments/20140212/ad1be4fc/attachment-0003.obj>