Description of problem: --> Processing Dependency: ovirt-engine-tools-backup = 4.0.0-0.0.master.20160323171719.git71fa3c8.el7.centos for package: ovirt-engine-tools-4.0.0-0.0.master.20160323171719.git71fa3c8.el7.centos.noarch --> Running transaction check ---> Package otopi-java.noarch 0:1.4.1-0.0.master.20151119131058.gitf1f8b20.el7 will be updated ---> Package otopi-java.noarch 0:1.5.0-0.0.master.20160323144840.gite04c16c.el7 will be an update ---> Package ovirt-engine-tools-backup.noarch 0:4.0.0-0.0.master.20160323171719.git71fa3c8.el7.centos will be updated --> Processing Dependency: ovirt-engine-tools-backup = 4.0.0-0.0.master.20160323171719.git71fa3c8.el7.centos for package: ovirt-engine-tools-4.0.0-0.0.master.20160323171719.git71fa3c8.el7.centos.noarch --> Finished Dependency Resolution Error: Package: ovirt-engine-tools-4.0.0-0.0.master.20160323171719.git71fa3c8.el7.centos.noarch (@upgrade_from_0) Requires: ovirt-engine-tools-backup = 4.0.0-0.0.master.20160323171719.git71fa3c8.el7.centos Removing: ovirt-engine-tools-backup-4.0.0-0.0.master.20160323171719.git71fa3c8.el7.centos.noarch (@upgrade_from_0) ovirt-engine-tools-backup = 4.0.0-0.0.master.20160323171719.git71fa3c8.el7.centos Updated By: ovirt-engine-tools-backup-4.0.0-0.0.master.20160324164357.git0b27b98.el7.centos.noarch (upgrade_to_2) ovirt-engine-tools-backup = 4.0.0-0.0.master.20160324164357.git0b27b98.el7.centos Available: ovirt-engine-tools-backup-4.0.0-0.0.master.20160322051336.git3e126db.el7.centos.noarch (upgrade_from_0) ovirt-engine-tools-backup = 4.0.0-0.0.master.20160322051336.git3e126db.el7.centos Available: ovirt-engine-tools-backup-4.0.0-0.0.master.20160322111609.gita8e07cd.el7.centos.noarch (upgrade_from_0) ovirt-engine-tools-backup = 4.0.0-0.0.master.20160322111609.gita8e07cd.el7.centos Available: ovirt-engine-tools-backup-4.0.0-0.0.master.20160322171551.git6cdf188.el7.centos.noarch (upgrade_from_0) ovirt-engine-tools-backup = 4.0.0-0.0.master.20160322171551.git6cdf188.el7.centos Available: ovirt-engine-tools-backup-4.0.0-0.0.master.20160323051331.git6cdf188.el7.centos.noarch (upgrade_from_0) ovirt-engine-tools-backup = 4.0.0-0.0.master.20160323051331.git6cdf188.el7.centos You could try using --skip-broken to work around the problem Version-Release number of selected component (if applicable): How reproducible: Detected by Jenkins at http://jenkins.ovirt.org/job/ovirt-engine_master_upgrade-from-master_el7_merged/2457/console Steps to Reproduce: 1. install a 4.0 nightly snapshot 2. update to a newer nightly snapshot 3. Actual results: Upgrade fails Expected results: Upgrade works
This bug was accidentally moved from POST to MODIFIED via an error in automation, please see mmccune with any questions
Waiting for a new build (for testing update)
Use "yum update rhevm-setup" (according to the documentation for updating rhevm) works but executing "yum update" doesn't. Users should be able to update system (all other packages) via command "yum update". Now users must use "yum update --exclude=rhevm-tools-backup" or update rhevm-setup and do engine-setup at first. So I think, this isn't okay ? versions: update 3.6.5-2 to 3.6.5-4 steps: 1 install 3.6.5-2 2. engine-setup 3. add repo 3.6.5-4 + yum update #yum update Loaded plugins: product-id, search-disabled-repos, security, versionlock Setting up Update Process Resolving Dependencies --> Running transaction check ---> Package rhevm-extensions-api-impl.noarch 0:3.6.5.1-0.1.el6 will be updated ---> Package rhevm-extensions-api-impl.noarch 0:3.6.5.3-0.1.el6 will be an update ---> Package rhevm-lib.noarch 0:3.6.5.1-0.1.el6 will be updated ---> Package rhevm-lib.noarch 0:3.6.5.3-0.1.el6 will be an update ---> Package rhevm-setup.noarch 0:3.6.5.1-0.1.el6 will be updated ---> Package rhevm-setup.noarch 0:3.6.5.3-0.1.el6 will be an update ---> Package rhevm-setup-base.noarch 0:3.6.5.1-0.1.el6 will be updated ---> Package rhevm-setup-base.noarch 0:3.6.5.3-0.1.el6 will be an update ---> Package rhevm-setup-plugin-ovirt-engine.noarch 0:3.6.5.1-0.1.el6 will be updated ---> Package rhevm-setup-plugin-ovirt-engine.noarch 0:3.6.5.3-0.1.el6 will be an update ---> Package rhevm-setup-plugin-ovirt-engine-common.noarch 0:3.6.5.1-0.1.el6 will be updated ---> Package rhevm-setup-plugin-ovirt-engine-common.noarch 0:3.6.5.3-0.1.el6 will be an update ---> Package rhevm-setup-plugin-vmconsole-proxy-helper.noarch 0:3.6.5.1-0.1.el6 will be updated ---> Package rhevm-setup-plugin-vmconsole-proxy-helper.noarch 0:3.6.5.3-0.1.el6 will be an update ---> Package rhevm-setup-plugin-websocket-proxy.noarch 0:3.6.5.1-0.1.el6 will be updated ---> Package rhevm-setup-plugin-websocket-proxy.noarch 0:3.6.5.3-0.1.el6 will be an update ---> Package rhevm-setup-plugins.noarch 0:3.6.3-1.el6ev will be updated ---> Package rhevm-setup-plugins.noarch 0:3.6.4-1.el6ev will be an update ---> Package rhevm-tools-backup.noarch 0:3.6.5.1-0.1.el6 will be updated --> Processing Dependency: rhevm-tools-backup = 3.6.5.1-0.1.el6 for package: rhevm-tools-3.6.5.1-0.1.el6.noarch ---> Package rhevm-tools-backup.noarch 0:3.6.5.3-0.1.el6 will be an update ---> Package rhevm-vmconsole-proxy-helper.noarch 0:3.6.5.1-0.1.el6 will be updated ---> Package rhevm-vmconsole-proxy-helper.noarch 0:3.6.5.3-0.1.el6 will be an update ---> Package rhevm-websocket-proxy.noarch 0:3.6.5.1-0.1.el6 will be updated ---> Package rhevm-websocket-proxy.noarch 0:3.6.5.3-0.1.el6 will be an update --> Finished Dependency Resolution Error: Package: rhevm-tools-3.6.5.1-0.1.el6.noarch (@rhevm-3.6.5-2) Requires: rhevm-tools-backup = 3.6.5.1-0.1.el6 Removing: rhevm-tools-backup-3.6.5.1-0.1.el6.noarch (@rhevm-3.6.5-2) rhevm-tools-backup = 3.6.5.1-0.1.el6 Updated By: rhevm-tools-backup-3.6.5.3-0.1.el6.noarch (rhevm-3.6.5-4) rhevm-tools-backup = 3.6.5.3-0.1.el6 Available: rhevm-tools-backup-3.6.5-0.1.el6.noarch (rhevm-3.6.5-1) rhevm-tools-backup = 3.6.5-0.1.el6
I guess that the simplest solution is to also versionlock rhevm-tools-backup. Can you please verify? Thanks. You can do that manually by editing /etc/yum/pluginconf.d/versionlock.list .
Yes, I only add "rhevm-tools-backup-3.6.5.1-0.1.el6.noarch" and now it's working.
Target release should be placed once a package build is known to fix a issue. Since this bug is not modified, the target version has been reset. Please use target milestone to plan a fix for a oVirt release.
Current status: The original bug was: Installing an affected version of an engine prevents further upgrades (by preventing upgrading the setup packages). A patch to fix this is merged. This introduced a new bug, which prevents 'yum update'. A workaround: yum update -x \*-tools-backup A fix for this, which is to also versionlock this package, is currently pending merge.
This is still failing when upgrading to 3.6.6-1 from either 3.6.5-1 or 3.6.5-5 with the same error as in comment 3 [root@pm-test1 ~]# yum update Loaded plugins: product-id, search-disabled-repos, security, versionlock Setting up Update Process rhevm36 | 2.9 kB 00:00 rhevm36/primary_db | 42 kB 00:00 Resolving Dependencies --> Running transaction check ---> Package ovirt-vmconsole.noarch 0:1.0.0-1.el6ev will be updated ---> Package ovirt-vmconsole.noarch 0:1.0.2-2.el6ev will be an update ---> Package ovirt-vmconsole-proxy.noarch 0:1.0.0-1.el6ev will be updated ---> Package ovirt-vmconsole-proxy.noarch 0:1.0.2-2.el6ev will be an update ---> Package rhev-guest-tools-iso.noarch 0:3.6-5.el6ev will be updated ---> Package rhev-guest-tools-iso.noarch 0:3.6-6.el6ev will be an update ---> Package rhevm-dwh-setup.noarch 0:3.6.2-1.el6ev will be updated ---> Package rhevm-dwh-setup.noarch 0:3.6.6-1.el6ev will be an update ---> Package rhevm-extensions-api-impl.noarch 0:3.6.5.3-0.1.el6 will be updated ---> Package rhevm-extensions-api-impl.noarch 0:3.6.6-0.1.el6 will be an update ---> Package rhevm-lib.noarch 0:3.6.5.3-0.1.el6 will be updated ---> Package rhevm-lib.noarch 0:3.6.6-0.1.el6 will be an update ---> Package rhevm-setup.noarch 0:3.6.5.3-0.1.el6 will be updated ---> Package rhevm-setup.noarch 0:3.6.6-0.1.el6 will be an update ---> Package rhevm-setup-base.noarch 0:3.6.5.3-0.1.el6 will be updated ---> Package rhevm-setup-base.noarch 0:3.6.6-0.1.el6 will be an update ---> Package rhevm-setup-plugin-ovirt-engine.noarch 0:3.6.5.3-0.1.el6 will be updated ---> Package rhevm-setup-plugin-ovirt-engine.noarch 0:3.6.6-0.1.el6 will be an update ---> Package rhevm-setup-plugin-ovirt-engine-common.noarch 0:3.6.5.3-0.1.el6 will be updated ---> Package rhevm-setup-plugin-ovirt-engine-common.noarch 0:3.6.6-0.1.el6 will be an update ---> Package rhevm-setup-plugin-vmconsole-proxy-helper.noarch 0:3.6.5.3-0.1.el6 will be updated ---> Package rhevm-setup-plugin-vmconsole-proxy-helper.noarch 0:3.6.6-0.1.el6 will be an update ---> Package rhevm-setup-plugin-websocket-proxy.noarch 0:3.6.5.3-0.1.el6 will be updated ---> Package rhevm-setup-plugin-websocket-proxy.noarch 0:3.6.6-0.1.el6 will be an update ---> Package rhevm-setup-plugins.noarch 0:3.6.4-1.el6ev will be updated ---> Package rhevm-setup-plugins.noarch 0:3.6.5-1.el6ev will be an update ---> Package rhevm-tools-backup.noarch 0:3.6.5.3-0.1.el6 will be updated --> Processing Dependency: rhevm-tools-backup = 3.6.5.3-0.1.el6 for package: rhevm-tools-3.6.5.3-0.1.el6.noarch ---> Package rhevm-tools-backup.noarch 0:3.6.6-0.1.el6 will be an update ---> Package rhevm-vmconsole-proxy-helper.noarch 0:3.6.5.3-0.1.el6 will be updated ---> Package rhevm-vmconsole-proxy-helper.noarch 0:3.6.6-0.1.el6 will be an update ---> Package rhevm-websocket-proxy.noarch 0:3.6.5.3-0.1.el6 will be updated ---> Package rhevm-websocket-proxy.noarch 0:3.6.6-0.1.el6 will be an update --> Finished Dependency Resolution Error: Package: rhevm-tools-3.6.5.3-0.1.el6.noarch (@rhevm36) Requires: rhevm-tools-backup = 3.6.5.3-0.1.el6 Removing: rhevm-tools-backup-3.6.5.3-0.1.el6.noarch (@rhevm36) rhevm-tools-backup = 3.6.5.3-0.1.el6 Updated By: rhevm-tools-backup-3.6.6-0.1.el6.noarch (rhevm36) rhevm-tools-backup = 3.6.6-0.1.el6 You could try using --skip-broken to work around the problem You could try running: rpm -Va --nofiles --nodigest
Moving back to ON_QA: version locking has been added in 3.6.6 so if you upgrade from 3.6.5 to 3.6.6 you still have the issue. This won't happen upgrading from 3.6.6 to 3.6.6.1(if we'll have it) or 3.6.7. In order to verify this bug in 3.6.6 check if the package has been added to version lock when installing 3.6.6 or add it to version lock in 3.6.5 manually and test upgrade from there.
Upgrade from 3.6.6 succeeded and the package was added to version lock.