Open Stack

On Fri, Apr 10, 2015 at 04:26:01PM +0800, ZhiQiang Fan wrote:
> not pyhton-novaclient only, all openstack project clients have fail gate
> for stable/icehouse and stable/juno
> 
In some cases stable/icehouse doesn't fail (like in cinderclient), but
you are right, they are failing everywhere.

> since we have pinned them in global requirements, so new changes in master
> should not run stable gate any more, otherwise, version conflict will be
> raised.

When you say they should not be run anymore you mean from now on or for
the moment?

Because I've seen in some cases that they mention they will add them
later once a stable/juno branch is added to the client.

I have seen in some cases that requirements have been changed, for
example from <=1.1.0 to <1.2.0, to be able to keep running these tests
[1][2]. Is this not a recommended change?

I'm asking because that's the path I've taken to fix this in
cinderclient [3][4]


Cheers,
Gorka.

[1] https://review.openstack.org/#/c/172718/
[2] https://review.openstack.org/#/c/172150/
[3] https://review.openstack.org/173250
[4] https://review.openstack.org/173256

> 
> On Fri, Apr 10, 2015 at 1:02 PM, melanie witt <melwittt at gmail.com> wrote:
> 
> > 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)
> >
> __________________________________________________________________________
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe:
> OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev