+++ This bug is a downstream clone. The original bug is: +++ +++ bug 1543526 +++ ====================================================================== Description of problem: This: 1. Install and setup rhv 4.1 2. Add current rhv 4.2 repo 3. yum update currently fails with [1]. Above flow is not officially supported, we always say to update only setup packages. However, when we get bug reports about it breaking, we usually fix them, usually by adding relevant packages to versionlock.list. The fix here is somewhat more delicate, because we renamed rhevm to rhvm and rhevm-branding-rhev to rhvm-branding-rhv. Now verified that applying [2] to /etc fixes it. If we want to have this fix, we have to: 1. Open a bug on 4.1 to do [2] - to versionlock rhevm-branding-rhev and to add 'follow_obsoletes = 1' to versionlock.conf. 2. Make rhv 4.2 prevent upgrade to 4.2 from < 4.1.10 Then, people trying to upgrade from 4.1.9 to 4.2 should get a similar error message, but the fix will be more obvious - first upgrade to 4.1.10. We never patched versionlock.conf, but I can't think of big potential problems doing so. [1] --> Finished Dependency Resolution Error: Package: ovirt-engine-4.1.8.2-0.1.el7.noarch (@rhv-4.1.8) Requires: rhevm = 4.1.8.2-0.1.el7 Removing: rhevm-4.1.8.2-0.1.el7.noarch (@rhv-4.1.8) rhevm = 4.1.8.2-0.1.el7 Obsoleted By: rhvm-4.2.1.6-0.1.el7.noarch (rhv-4.2.1) rhevm = 4.2.1.6 Error: Package: ovirt-engine-backend-4.1.8.2-0.1.el7.noarch (@rhv-4.1.8) Requires: rhevm-branding-rhev >= 4.0.0 Removing: rhevm-branding-rhev-4.1.8-1.el7ev.noarch (@rhv-4.1.8) rhevm-branding-rhev = 4.1.8-1.el7ev Obsoleted By: rhvm-branding-rhv-4.2.1-1.el7ev.noarch (rhv-4.2.1) Not found Available: rhevm-branding-rhev-4.1.0-2.el7ev.noarch (rhv-4.1.4) rhevm-branding-rhev = 4.1.0-2.el7ev Error: Package: rhvm-4.2.1.6-0.1.el7.noarch (rhv-4.2.1) Requires: ovirt-engine = 4.2.1.6-0.1.el7 Installed: ovirt-engine-4.1.8.2-0.1.el7.noarch (@rhv-4.1.8) ovirt-engine = 4.1.8.2-0.1.el7 You could try using --skip-broken to work around the problem You could try running: rpm -Va --nofiles --nodigest [2] diff --git a/yum/pluginconf.d/versionlock.conf b/yum/pluginconf.d/versionlock.conf index 4e997da..428aea6 100644 --- a/yum/pluginconf.d/versionlock.conf +++ b/yum/pluginconf.d/versionlock.conf @@ -2,4 +2,4 @@ enabled = 1 locklist = /etc/yum/pluginconf.d/versionlock.list # Uncomment this to lock out "upgrade via. obsoletes" etc. (slower) -# follow_obsoletes = 1 +follow_obsoletes = 1 diff --git a/yum/pluginconf.d/versionlock.list b/yum/pluginconf.d/versionlock.list index 11470b0..dacf95c 100644 --- a/yum/pluginconf.d/versionlock.list +++ b/yum/pluginconf.d/versionlock.list @@ -12,3 +12,4 @@ redhat-support-plugin-rhev-4.1.0-1.el7.noarch ovirt-engine-tools-4.1.8.2-0.1.el7.noarch ovirt-engine-extension-aaa-jdbc-1.1.6-1.el7ev.noarch ovirt-engine-userportal-4.1.8.2-0.1.el7.noarch +rhevm-branding-rhev-4.1.8-1.el7ev.noarch (Originally by didi)
According to https://access.redhat.com/documentation/en-us/red_hat_virtualization/4.1/html/upgrade_guide/chap-updates_between_minor_releases#Upgrading_between_Minor_Releases the correct procedure for updating the manager is: # yum update ovirt\*setup\* # engine-setup # yum update and this avoid above output from yum. Despite I don't think it's nice to see above message when issuing a generic yum update ignoring the documentation, I think we can close this bug. Yaniv, what do you think? (Originally by Sandro Bonazzola)
Let's inject the new package name in 4.1.10. (Originally by Sandro Bonazzola)
Let's also open a bug on yum versionlock plugin, not blocking the package renamed providing version locked packages. (Originally by Sandro Bonazzola)
(In reply to Sandro Bonazzola from comment #4) > Let's also open a bug on yum versionlock plugin, not blocking the package > renamed providing version locked packages. Sorry, didn't follow. AFAIU both of the changes can/should be done in rhevm-setup-plugins-4.1. It might make sense to patch versionlock.conf in upstream, but not much sense - we didn't rename anything there and I do not think we intend to, soon. (Originally by didi)
(In reply to Yedidyah Bar David from comment #5) > (In reply to Sandro Bonazzola from comment #4) > > Let's also open a bug on yum versionlock plugin, not blocking the package > > renamed providing version locked packages. > > Sorry, didn't follow. AFAIU both of the changes can/should be done in > rhevm-setup-plugins-4.1. It might make sense to patch versionlock.conf in > upstream, but not much sense - we didn't rename anything there and I do not > think we intend to, soon. fixing in rhevm-setup-plugins-4.1 is fine for 4.1.10. Now I see the follow_obsoletes in versionlock conf, so I think we should set it. No need to open a platform bug. (Originally by Sandro Bonazzola)
ok, Jan 25 11:30:25 Installed: rhevm-4.1.9.1-0.1.el7.noarch Feb 23 13:18:29 Updated: rhevm-4.1.10.1-0.1.el7.noarch
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2018:0564
BZ<2>Jira Resync