[openstack-dev] [nova] novaclient 'stable-compat-jobs-{name}' broken
melanie witt
melwittt at gmail.com
Fri Apr 10 05:02:29 UTC 2015
Hi all,
The following 'stable-compat-jobs-{name}' build jobs have been broken the past two days, blocking all novaclient patches from passing jenkins checks:
gate-tempest-dsvm-neutron-src-python-novaclient-icehouse
gate-tempest-dsvm-neutron-src-python-novaclient-juno
The original purpose of these jobs was to check that patches proposed to master wouldn't break in stable branches. This was before we started pinning novaclient versions on stable branches. Now that we've pinned, the way these jobs were passing was by installing the current novaclient, then uninstalling it, then installing a version from pypi that fits within the global requirements for the branch in question (icehouse or juno), then running the tests.
Well, recently this stopped working because for some reason, devstack is no longer able to uninstall the latest version:
Found existing installation: python-novaclient 2.23.0.post14
Can't uninstall 'python-novaclient'. No files were found to uninstall.
And then I see the following error as a result:
pkg_resources.ContextualVersionConflict: (python-novaclient 2.23.0.post14 (/opt/stack/new/python-novaclient), Requirement.parse('python-novaclient<=2.20.0,>=2.18.0'), set(['ceilometer']))
I asked about this in #openstack-infra and was told we really shouldn't be running the "src" build jobs on patches proposed to master anyhow, and that it's not the right flow for devstack to install the latest, then uninstall it, then install an older global reqs compatible version anyway.
Given that, is it okay if I propose a patch to remove the 'stable-compat-jobs-{name}' build jobs for python-novaclient in project-config?
Then after that, how are we supposed to go about cutting stable branches for novaclient? And how can we get the 'stable-compat-jobs-{name}' jobs running on only those respective branches? In project-config I didn't understand how to limit build jobs to only patches proposed to a stable branch.
I'd appreciate any insights.
Thanks,
melanie (melwitt)
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 496 bytes
Desc: Message signed with OpenPGP using GPGMail
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20150409/f4210fd1/attachment.pgp>
More information about the OpenStack-dev
mailing list