Bug 1056470
| Summary: | python-cpopen-1.3 is not providing obsoleted package. | ||
|---|---|---|---|
| Product: | [Retired] oVirt | Reporter: | Sandro Bonazzola <sbonazzo> |
| Component: | vdsm | Assignee: | Dan Kenigsberg <danken> |
| Status: | CLOSED UPSTREAM | QA Contact: | Aharon Canan <acanan> |
| Severity: | urgent | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 3.3 | CC: | abaron, acathrow, bazulay, bronhaim, danken, dougsland, eedri, gklein, iheim, jdorff, mgoldboi, ms, obasan, rstory, sbonazzo, s.kieske, yeylon |
| Target Milestone: | --- | Keywords: | AutomationBlocker, AutomationTriaged |
| Target Release: | 3.3.3 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | integration | ||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | 1056464 | Environment: | |
| Last Closed: | 2014-02-04 12:28:28 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: | |||
| Bug Depends On: | 1056464 | ||
| Bug Blocks: | |||
|
Description
Sandro Bonazzola
2014-01-22 09:30:58 UTC
(I did not notice that a cpopen bug already exists.) cpopen should better to keep providing vdsm-python-cpopen-4.13. IMO there's nothing to do here, when it comes to Vdsm. Sandro, I fail to reproduce the issue on my f20: $ rpm -q --provides python-cpopen python-cpopen = 1.3-1.fc20 python-cpopen(x86-64) = 1.3-1.fc20 vdsm-python-cpopen = 4.13.2 $ rpm --test -Uv vdsm-xmlrpc-4.13.3-2.fc19.noarch.rpm vdsm-python-4.13.3-2.fc19.x86_64.rpm Preparing packages... $ echo $? 0 Which python-cpopen release do you see the issue? (In reply to Dan Kenigsberg from comment #2) > Sandro, I fail to reproduce the issue on my f20: > > $ rpm -q --provides python-cpopen > python-cpopen = 1.3-1.fc20 > python-cpopen(x86-64) = 1.3-1.fc20 > vdsm-python-cpopen = 4.13.2 > > $ rpm --test -Uv vdsm-xmlrpc-4.13.3-2.fc19.noarch.rpm > vdsm-python-4.13.3-2.fc19.x86_64.rpm > Preparing packages... > $ echo $? > 0 > > Which python-cpopen release do you see the issue? Using ovirt-stable repository which provides vdsm-python-4.13.3-2 for EL6 and F19. # yum remove "vdsm*" "python-cpopen*" # yum install vdsm it fails with above error. # yum install python-cpopen # rpm -qv python-cpopen python-cpopen-1.3-1.fc19.x86_64 # rpm -qv python-cpopen --provides manual: python-cpopen = 1.3-1.fc19 manual: python-cpopen(x86-64) = 1.3-1.fc19 manual: vdsm-python-cpopen = 4.13.2 # rpm -qv python-cpopen --obsoletes manual: vdsm-python-cpopen <= 4.14 You're obsoleting <=4.14 and providing 4.13.2 but 4.13.3-2 is required by vdsm, breaking dependencies. That should probably be something like: Provides: vdsm-python-cpopen = 4.14.0 Obsoletes: vdsm-python-cpopen < 4.14.0 Maybe also for x86-64 Provides: vdsm-python-cpopen(x86-64) = 4.14.0 Obsoletes: vdsm-python-cpopen(x86-64) < 4.14.0 And for i686: Provides: vdsm-python-cpopen(i686) = 4.14.0 Obsoletes: vdsm-python-cpopen(i686) < 4.14.0 See https://fedoraproject.org/wiki/Packaging:Guidelines#Renaming.2FReplacing_Existing_Packages I'm seeing this too.. EL 6.5, all up to date. I can't add a new host to my oVirt cluster.. fix asap, pretty please! Someone on the ovirt users mailing list has a work-around: manually installing python-cpopen on the node before adding node in the engine. Worked for me! Since python-cpopen issue is not relevant anymore on oVirt thanks to the VDSM dependencies fixes introduced in last rpm build, I'm closing this with resolution UPSTREAM. python-cpopen broken provides will be handled on Fedora BZ #1056464. |