On Wed, Nov 20, 2013 at 01:04:26PM -0500, Nir Soffer wrote:
----- Original Message -----
From: "Ewoud Kohl van Wijngaarden" ewoud@kohlvanwijngaarden.nl To: "Nir Soffer" nsoffer@redhat.com Sent: Wednesday, November 20, 2013 7:55:30 PM Subject: Re: Failing puppet runs due to python-cpopen
On Wed, Nov 20, 2013 at 12:52:48PM -0500, Nir Soffer wrote:
----- Original Message -----
From: "Ewoud Kohl van Wijngaarden" ewoud+ovirt@kohlvanwijngaarden.nl To: infra@ovirt.org, vdsm-devel@lists.fedorahosted.org Sent: Wednesday, November 20, 2013 7:45:39 PM Subject: Failing puppet runs due to python-cpopen
Hello all,
Currently we attempt to install python-cpopen, but puppet fails to do this. When I manually run it:
[root@jenkins-slave-vm01 ~]# yum install python-cpopen Loaded plugins: versionlock Resolving Dependencies --> Running transaction check ---> Package python-cpopen.x86_64 0:1.2.3-2.fc19 will be installed Removing python-cpopen.x86_64 0:1.2.3-2.fc19 - u due to obsoletes from installed vdsm-python-cpopen-4.13.0-9.fc19.x86_64 --> Restarting Dependency Resolution with new changes. --> Running transaction check ---> Package python-cpopen.x86_64 0:1.2.3-2.fc19 will be installed --> Finished Dependency Resolution [root@jenkins-slave-vm01 ~]#
Any advice here?
On RHEL you have to remove vdsm-python-cpopen before it would install python-cpopen.
Maybe the automated job should check if vdsm-python-cpopen is installed and remove it?
But this is fc19. Should I still manually fix it?
If you want to install vdsm, you probably should :-)
Personally I don't need to install vdsm, but jenkins insists :-). Should we no longer ensure python-cpopen is installed and just rely on vdsm to do the right thing?
Also, I accidentally replied just to you instead of the list, so adding again.