update: i tested this with new python-cpopen and it seems to work. so i guess we should push the new version into fedora and el soon to resolve this.
Eyal. ----- Original Message ----- > From: "Eyal Edri" <ee...@redhat.com> > To: "Dan Kenigsberg" <dan...@redhat.com>, "Sandro Bonazzola" > <sbona...@redhat.com>, "Kiril Nesenko" > <knese...@redhat.com> > Cc: infra@ovirt.org > Sent: Thursday, January 2, 2014 5:29:29 PM > Subject: Re: Another cpopen missing failure > > ok, > > sandro - can we update the ovirt-testing repo with the latest pkg? > or remove the offending one? > > eyal. > > ----- Original Message ----- > > From: "Dan Kenigsberg" <dan...@redhat.com> > > To: "Eyal Edri" <ee...@redhat.com> > > Cc: "Ewoud Kohl van Wijngaarden" <ewoud+ov...@kohlvanwijngaarden.nl>, > > infra@ovirt.org > > Sent: Thursday, January 2, 2014 4:50:45 PM > > Subject: Re: Another cpopen missing failure > > > > 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 > > > > ovirt-3.3's Vdsm builds vdsm-python-cpopen - as it always has and always > > will. We cannot change history, and we shouldn't make such a change in a > > stable branch. > > > > master's Vdsm does not build that package and does not require it. > > > > > 2. why spec file brings it when you try to install python-cpopen. > > > > http://resources.ovirt.org/releases/updates-testing/rpm/Fedora/19/x86_64/ > > is enabled on that slave, and it carries > > vdsm-python-4.13.2-1.fc19.x86_64.rpm which provides python-cpopen=1.2.3 > > > > Yum prefers to take it over the available version from fedora. This > > might be related to the fact that > > https://admin.fedoraproject.org/updates/FEDORA-2013-23216/python-cpopen-1.2.3-5.fc19 > > is stuck in testing mode for quite some time. Your karma may hasten > > things there. > > > > I share Ewoud's opinion: since some jobs need python-cpopen and some > > conflict with it, it should not be part of the platform handled by > > puppet, but job-specific. > > > > On the mean while we should disable the updates-testing repo, or drop > > the old ovirt-3.3 stuff from it, or put python-cpopen-1.2.3-5 there. > > > > Dan. > > > _______________________________________________ > Infra mailing list > Infra@ovirt.org > http://lists.ovirt.org/mailman/listinfo/infra > _______________________________________________ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra