Bug 1545059
Summary: | [downstream clone - 4.1.10] yum update between RHV 4.1.9 and current 4.2 fails | ||
---|---|---|---|
Product: | Red Hat Enterprise Virtualization Manager | Reporter: | rhev-integ |
Component: | rhevm-setup-plugins | Assignee: | Yedidyah Bar David <didi> |
Status: | CLOSED ERRATA | QA Contact: | Jiri Belka <jbelka> |
Severity: | medium | Docs Contact: | |
Priority: | unspecified | ||
Version: | unspecified | CC: | bburmest, didi, lsurette, rbalakri, Rhev-m-bugs, sbonazzo, srevivo, ykaul, ylavi |
Target Milestone: | ovirt-4.1.10 | Keywords: | ZStream |
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | rhevm-setup-plugins-4.1.5-1.el7ev | Doc Type: | Bug Fix |
Doc Text: |
rhevm-setup-plugin now version-locks rhevm-branding-rhev in order to ease future upgrades to RHV 4.2.
|
Story Points: | --- |
Clone Of: | 1543526 | Environment: | |
Last Closed: | 2018-03-20 16:40:23 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | Integration | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | 1543526 | ||
Bug Blocks: |
Description
rhev-integ
2018-02-14 07:56:48 UTC
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) 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 |