Another cpopen missing failure

Thu Jan 2 13:01:52 UTC 2014

On Wed, Jan 01, 2014 at 02:10:54PM -0500, Eyal Edri wrote:
> the problem is that one vdsm jobs needs python-cpopen (like unit tests),
> while another job (like vdsm install sanity) fails on it cause of conflict with vdsm-python-cpopen,
> so puppet does what it should like all other pkg.
> 
> what's wrong is:
> 1. why vdsm still builds vdsm-python-cpopen if it's not needed 

Do you really want to change this for released / still supported
versions?

> 2. why spec file brings it when you try to install python-cpopen.
> 
> e.
> 
> ----- Original Message -----
> > From: "Ewoud Kohl van Wijngaarden" <ewoud+ovirt at kohlvanwijngaarden.nl>
> > To: "Eyal Edri" <eedri at redhat.com>
> > Cc: "Nir Soffer" <nsoffer at redhat.com>, infra at ovirt.org
> > Sent: Wednesday, January 1, 2014 7:52:36 PM
> > Subject: Re: Another cpopen missing failure
> > 
> > I think it's a problem that puppet still tries to install python-cpopen
> > which is wrong and the reason jenkins-slave-vm01 keeps going into the
> > puppet error state:
> > 
> > <<<EOF
> > change from absent to latest failed: Could not update: Execution of
> > '/usr/bin/yum -d 0 -e 0 -y install python-cpopen' returned 1:
> > 
> > Transaction check error:
> >   file /usr/lib64/python2.7/site-packages/cpopen/__init__.py from install of
> >   python-cpopen-1.2.3-4.fc19.x86_64 conflicts with file from package
> >   vdsm-python-cpopen-4.13.2-1.fc19.x86_64
> >   file /usr/lib64/python2.7/site-packages/cpopen/__init__.pyc from install of
> >   python-cpopen-1.2.3-4.fc19.x86_64 conflicts with file from package
> >   vdsm-python-cpopen-4.13.2-1.fc19.x86_64
> >   file /usr/lib64/python2.7/site-packages/cpopen/__init__.pyo from install of
> >   python-cpopen-1.2.3-4.fc19.x86_64 conflicts with file from package
> >   vdsm-python-cpopen-4.13.2-1.fc19.x86_64
> >   file /usr/lib64/python2.7/site-packages/cpopen/cpopen.so from install of
> >   python-cpopen-1.2.3-4.fc19.x86_64 conflicts with file from package
> >   vdsm-python-cpopen-4.13.2-1.fc19.x86_64
> > 
> > Error Summary
> > -------------
> > EOF
> > 
> > I thinkt he solution is to re-submit http://gerrit.ovirt.org/22140
> > against production and have the VDSM job ensure the proper version is
> > installed or ensure either version can be used so we no longer need
> > vdsm-python-cpopen at all. Puppet enforces state and if a jenkins job
> > needs a variable state (ie sometimes X, sometimes Y), puppet is the
> > wrong tool to use and it becomes the jobs responsibility.
> > 
> > On Wed, Jan 01, 2014 at 07:07:34AM -0500, Eyal Edri wrote:
> > > i still think it's a problem with vdsm master (of one of it's deps) bring
> > > it:
> > > http://jenkins.ovirt.org/job/vdsm_master_install_rpm_sanity_gerrit/label=fedora19/188/console
> > > 
> > > 
> > > Marking
> > > /home/jenkins/workspace/vdsm_master_install_rpm_sanity_gerrit/label/fedora19/rpms/vdsm-python-zombiereaper-4.13.0-274.git4f2c481.fc19.noarch.rpm
> > > to be installed
> > > Resolving Dependencies
> > > --> Running transaction check
> > > ---> Package vdsm.x86_64 0:4.13.0-274.git4f2c481.fc19 will be installed
> > > --> Processing Dependency: python-cpopen >= 1.2.3-5 for package:
> > > vdsm-4.13.0-274.git4f2c481.fc19.x86_64
> > > ---> Package vdsm-python.x86_64 0:4.13.0-274.git4f2c481.fc19 will be
> > > installed
> > > ---> Package vdsm-python-zombiereaper.noarch 0:4.13.0-274.git4f2c481.fc19
> > > will be installed
> > > ---> Package vdsm-xmlrpc.noarch 0:4.13.0-274.git4f2c481.fc19 will be
> > > installed
> > > --> Running transaction check
> > > ---> Package vdsm-python-cpopen.x86_64 0:4.13.2-1.fc19 will be installed
> > > --> Finished Dependency Resolution
> > > 
> > > ----- Original Message -----
> > > > From: "Nir Soffer" <nsoffer at redhat.com>
> > > > To: "Eyal Edri" <eedri at redhat.com>
> > > > Cc: infra at ovirt.org, "David Caro Estevez" <dcaroest at redhat.com>, "Yaniv
> > > > Bronheim" <ybronhei at redhat.com>, "Dan
> > > > Kenigsberg" <danken at redhat.com>
> > > > Sent: Wednesday, January 1, 2014 1:12:44 PM
> > > > Subject: Re: Another cpopen missing failure
> > > > 
> > > > ----- Original Message -----
> > > > > From: "Eyal Edri" <eedri at redhat.com>
> > > > > To: "Nir Soffer" <nsoffer at redhat.com>
> > > > > Cc: infra at ovirt.org, "David Caro Estevez" <dcaroest at redhat.com>
> > > > > Sent: Wednesday, January 1, 2014 1:06:11 PM
> > > > > Subject: Re: Another cpopen missing failure
> > > > > 
> > > > > and again this is caused by vdsm-python-cpopen installed on the host by
> > > > > another job probably.
> > > > > so either vdsm will fix this in the spec file so it will not conflict
> > > > > with
> > > > > each other,
> > > > > 
> > > > > or we need to find who's installing the vdsm-python-cpopen pkg.
> > > > 
> > > > This never ends :-)
> > > > 
> > > > How can we prevent such issues in the future?
> > > > 
> > > > > 
> > > > > 
> > > > > Eyal.
> > > > > 
> > > > > ----- Original Message -----
> > > > > > From: "Nir Soffer" <nsoffer at redhat.com>
> > > > > > To: infra at ovirt.org
> > > > > > Sent: Wednesday, January 1, 2014 12:23:44 PM
> > > > > > Subject: Another cpopen missing failure
> > > > > > 
> > > > > > Hi infra,
> > > > > > 
> > > > > > Another failure caused by missing cpopen:
> > > > > > http://jenkins.ovirt.org/job/vdsm_unit_tests_gerrit/6477/testReport/junit/nose.failure/Failure/runTest/
> > > > > > 
> > > > > > Can you check this?
> > > > > > _______________________________________________
> > > > > > Infra mailing list
> > > > > > Infra at ovirt.org
> > > > > > http://lists.ovirt.org/mailman/listinfo/infra
> > > > > > 
> > > > > 
> > > > 
> > > _______________________________________________
> > > Infra mailing list
> > > Infra at ovirt.org
> > > http://lists.ovirt.org/mailman/listinfo/infra
> > 