Bug 920678
| Summary: | upgrade fails because of rhevm-doc requires/conflict issue | ||||||
|---|---|---|---|---|---|---|---|
| Product: | Red Hat Enterprise Virtualization Manager | Reporter: | Jiri Belka <jbelka> | ||||
| Component: | rhevm-doc | Assignee: | Kiril Nesenko <knesenko> | ||||
| Status: | CLOSED ERRATA | QA Contact: | Jiri Belka <jbelka> | ||||
| Severity: | urgent | Docs Contact: | |||||
| Priority: | urgent | ||||||
| Version: | 3.2.0 | CC: | acathrow, alourie, bazulay, dfediuck, eedri, iheim, jkt, knesenko, lpeer, mgoldboi, Rhev-m-bugs, thildred, yeylon | ||||
| Target Milestone: | --- | Keywords: | Regression, TestBlocker | ||||
| Target Release: | 3.2.0 | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | integration | ||||||
| Fixed In Version: | rhevm-doc-3.2.0-0.3.beta.el6eng | Doc Type: | Bug Fix | ||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2013-08-26 10:44:08 UTC | Type: | Bug | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Embargoed: | |||||||
| Attachments: |
|
||||||
|
Description
Jiri Belka
2013-03-12 14:25:53 UTC
What we have today is: Conflict: rhevm < 3.2.0 Until the fix is released, the workaround for this issue: 1. Upgrade engine * run yum update rhevm-setup * run rhevm-upgrade 2. Upgrade the system * run yum update Hi Jiri 1. Please try the work around suggested in the previous comment. 2. Please elaborate a bit on the exact sequence of the actions: * was rhevm-doc installed on the system? 3. Please attach full logs of the engine upgrade. Thanks. /* clarification of comment #0 */ See is for BZ882284, bad typo. /* comment to comment #4 */ 1. for me workaround was obvious, force update to rhevm-doc with rpm --nodeps as this is circular dependency issue > Looks like circular dependency hell. rhevm-doc -> rhevm > 3.2.0 -> rhevm depends on rhevm-doc .... ???? 2. of course as rhevm installs rhevm-doc (and rhevm-doc requires rhevm) 3. included As BZ882284 states, they want to remove dependency on rhevm. So I think it should be removed, now rhevm-upgrade can check for its existence and upgrade it. And new installation? rhevm can still depend on rhevm-doc. New install: rhevm <- rhevm-doc New install: rhevm-doc /never installs rhevm/ Upgrade: rhevm-doc in versionlock.list /if this is why you put version because you were scared about version mismatch/ rhevm-upgrade upgrades to valid rhevm-doc version Created attachment 709720 [details]
engine upgrade logs
(In reply to comment #6) > /* clarification of comment #0 */ > > See is for BZ882284, bad typo. > > /* comment to comment #4 */ > > 1. for me workaround was obvious, force update to rhevm-doc with rpm > --nodeps as this is circular dependency issue > > > Looks like circular dependency hell. rhevm-doc -> rhevm > 3.2.0 -> rhevm depends on rhevm-doc .... ???? > > 2. of course as rhevm installs rhevm-doc (and rhevm-doc requires rhevm) > 3. included > > As BZ882284 states, they want to remove dependency on rhevm. So I think it > should be removed, now rhevm-upgrade can check for its existence and upgrade > it. And new installation? rhevm can still depend on rhevm-doc. +1 here, i don't see why this dependency on rhev is needed on docs. Simon, thoughts? > > New install: rhevm <- rhevm-doc > New install: rhevm-doc /never installs rhevm/ > Upgrade: rhevm-doc in versionlock.list /if this is why you put version > because you were scared about version mismatch/ > rhevm-upgrade upgrades to valid rhevm-doc version
> > As BZ882284 states, they want to remove dependency on rhevm. So I think it
> > should be removed, now rhevm-upgrade can check for its existence and upgrade
> > it. And new installation? rhevm can still depend on rhevm-doc.
>
> +1 here, i don't see why this dependency on rhev is needed on docs.
> Simon, thoughts?
As Itamar said less of an issue right now so let's resolve the quickest way.
For 4.0 we'll have to reconsider the entire version lock concept and see what can be done to break into packages that can be separately upgraded (and built)
ok, sf10.1. |