Due to changes in python-cpopen-1.3, VDSM provided by ovirt 3.3.2 can't be installed anymore on F19. +++ This bug was initially created as a clone of Bug #1056464 +++ python-cpopen-1.3 is not providing obsoleted package. In order to reproduce, enable ovirt-stable repository and: yum install vdsm --> Processing Dependency: vdsm-python-cpopen for package: vdsm-xmlrpc-4.13.2-1.fc19.noarch Package vdsm-python-cpopen is obsoleted by python-cpopen, but obsoleting package does not provide for requirements --> Finished Dependency Resolution Error: Package: vdsm-xmlrpc-4.13.2-1.fc19.noarch (ovirt-3.3.2) Requires: vdsm-python-cpopen Available: python-cpopen-1.3-1.fc19.x86_64 (updates) vdsm-python-cpopen = 4.13.2 Available: vdsm-python-cpopen-4.12.1-2.fc19.i686 (ovirt-stable) vdsm-python-cpopen = 4.12.1-2.fc19 Available: vdsm-python-cpopen-4.12.1-4.fc19.i686 (ovirt-stable) vdsm-python-cpopen = 4.12.1-4.fc19 Available: vdsm-python-cpopen-4.13.0-9.fc19.i686 (ovirt-stable) vdsm-python-cpopen = 4.13.0-9.fc19 Available: vdsm-python-cpopen-4.13.0-11.fc19.i686 (ovirt-stable) vdsm-python-cpopen = 4.13.0-11.fc19 Available: vdsm-python-cpopen-4.13.2-1.fc19.i686 (ovirt-3.3.2) vdsm-python-cpopen = 4.13.2-1.fc19 You could try using --skip-broken to work around the problem
(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!
I'm in the same state as comment 4. Can't add a host.
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.