Re: [Users] Problem with python-cpopen dependency on f19 AIO stable
I have the same issue on a CentOS node after updating it to 6.5:
Resolving Dependencies --> Running transaction check ---> Package python-cpopen.x86_64 0:1.2.3-4.el6 will be obsoleted ---> Package vdsm-python-cpopen.x86_64 0:4.13.0-11.el6 will be obsoleting --> Finished Dependency Resolution
Dependencies Resolved
======================================================================================================================================================== Package Arch Version Repository Size ======================================================================================================================================================== Installing: vdsm-python-cpopen x86_64 4.13.0-11.el6 ovirt-stable 19 k replacing python-cpopen.x86_64 1.2.3-4.el6
Transaction Summary ======================================================================================================================================================== Install 1 Package(s)
Total download size: 19 k Is this ok [y/N]: y
On a subsequent run of 'yum update', python-cpopen will replace vdsm-python-cpopen, and so on. Cheers, Martijn. Vinzenz Feenstra schreef op 5-12-2013 8:34:
Forwading to vdsm-devel
On 12/04/2013 08:59 AM, Gianluca Cecchi wrote:
Hello, since yesterday evening I have this sort of dependency problem with updates
yum update say
Resolving Dependencies --> Running transaction check ---> Package python-cpopen.x86_64 0:1.2.3-4.fc19 will be obsoleting ---> Package vdsm-python-cpopen.x86_64 0:4.13.0-11.fc19 will be obsoleted --> Finished Dependency Resolution
Dependencies Resolved
============================================================================================================================= Package Arch Version Repository Size ============================================================================================================================= Installing: python-cpopen x86_64 1.2.3-4.fc19 updates 19 k replacing vdsm-python-cpopen.x86_64 4.13.0-11.fc19
Transaction Summary ============================================================================================================================= Install 1 Package
If I go ahead and run yum update again I have:
Dependencies Resolved
============================================================================================================================= Package Arch Version Repository Size ============================================================================================================================= Installing: vdsm-python-cpopen x86_64 4.13.0-11.fc19 ovirt-stable 20 k replacing python-cpopen.x86_64 1.2.3-4.fc19
Transaction Summary ============================================================================================================================= Install 1 Package
and so again in a loop....
Gianluca _______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Joining two threads on that subject On Sun, Nov 24, 2013 at 11:32:55AM -0500, Yaniv Bronheim wrote:
Hey,
----- Original Message -----
From: "Nicholas Kesick" <cybertimber2000@hotmail.com> To: "oVirt Mailing List" <users@ovirt.org> Sent: Friday, November 22, 2013 6:55:23 PM Subject: [Users] Trouble Upgrading (Fedora)
I am having trouble upgrading on Fedora 19 to 3.3.1.
Two observations: 1) I can't find ovirt-engine-3.3.1, even after a yum clear all; yum update.
2) There is a dependency update circle involving python-cpopen-1.2.3-4.fc19.x86_64 and dsm-python-cpopen.x86_64 0:4.13.0-11.fc19
This issue is fine. Not so smoothly but we had to do that. cpopen package is published as part of vdsm code in ovirt-3.3 and before, On master branch we require python-cpopen formal package that is shipped with fedora\rhel currently .
Each time you'll switch between newer version of current master (3.4) to ovirt-3.3 or older you will notice this report
We should break this vicious cycle. I think it was intended to simplify "upgrade" from ovirt-3.4 to ovirt-3.3 on Jenkins slaves. But that's plain wrong on a wider context. The Jenkins issue should be solved explicitly by removing python-cpopen when vdsm-python-cpopen has to be installed. Dan.
Hi, was this resolved for EL 6.5? I'm currently planning to roll out EL 6.5 Nodes and would like to know how to circumvent this issue if it is still present? Am 05.12.2013 12:13, schrieb Martijn Grendelman:
I have the same issue on a CentOS node after updating it to 6.5:
Resolving Dependencies --> Running transaction check ---> Package python-cpopen.x86_64 0:1.2.3-4.el6 will be obsoleted ---> Package vdsm-python-cpopen.x86_64 0:4.13.0-11.el6 will be obsoleting --> Finished Dependency Resolution
Dependencies Resolved
======================================================================================================================================================== Package Arch Version Repository Size ======================================================================================================================================================== Installing: vdsm-python-cpopen x86_64 4.13.0-11.el6 ovirt-stable 19 k replacing python-cpopen.x86_64 1.2.3-4.el6
Transaction Summary ======================================================================================================================================================== Install 1 Package(s)
Total download size: 19 k Is this ok [y/N]: y
On a subsequent run of 'yum update', python-cpopen will replace vdsm-python-cpopen, and so on.
Vinzenz Feenstra schreef op 5-12-2013 8:34:
Forwading to vdsm-devel
On 12/04/2013 08:59 AM, Gianluca Cecchi wrote:
Hello, since yesterday evening I have this sort of dependency problem with updates
yum update say
Resolving Dependencies --> Running transaction check ---> Package python-cpopen.x86_64 0:1.2.3-4.fc19 will be obsoleting ---> Package vdsm-python-cpopen.x86_64 0:4.13.0-11.fc19 will be obsoleted --> Finished Dependency Resolution
Dependencies Resolved
============================================================================================================================= Package Arch Version Repository Size ============================================================================================================================= Installing: python-cpopen x86_64 1.2.3-4.fc19 updates 19 k replacing vdsm-python-cpopen.x86_64 4.13.0-11.fc19
Transaction Summary ============================================================================================================================= Install 1 Package
If I go ahead and run yum update again I have:
Dependencies Resolved
============================================================================================================================= Package Arch Version Repository Size ============================================================================================================================= Installing: vdsm-python-cpopen x86_64 4.13.0-11.fc19 ovirt-stable 20 k replacing python-cpopen.x86_64 1.2.3-4.fc19
Transaction Summary ============================================================================================================================= Install 1 Package
and so again in a loop....
Gianluca
-- Mit freundlichen Grüßen / Regards Sven Kieske Systemadministrator Mittwald CM Service GmbH & Co. KG Königsberger Straße 6 32339 Espelkamp T: +49-5772-293-100 F: +49-5772-293-333 https://www.mittwald.de Geschäftsführer: Robert Meyer St.Nr.: 331/5721/1033, USt-IdNr.: DE814773217, HRA 6640, AG Bad Oeynhausen Komplementärin: Robert Meyer Verwaltungs GmbH, HRB 13260, AG Bad Oeynhausen
participants (3)
-
Dan Kenigsberg -
Martijn Grendelman -
Sven Kieske