On Tue, Apr 21, 2015 at 12:10 PM, gordon chung <g...@live.ca> wrote: > ______________________________ > > Date: Tue, 21 Apr 2015 11:12:12 -0500 > > From: b...@acm.org > > To: openstack-dev@lists.openstack.org > > Subject: Re: [openstack-dev] [keystone] keystonemiddleware stable/juno > broken > > > > > > > > On Sun, Apr 19, 2015 at 2:21 PM, Brant Knudson > > <b...@acm.org<mailto:b...@acm.org>> wrote: > > > > Ever since the stable/juno branch was created for keystonemiddleware > > it's been broken and there are several changes piling up there. The fix > > for bug 1408838 "Tests fail with new oslo.utils 1.2.1" allows the tests > > to pass. I cherry-picked the fix here[1]. > > > > Based on the title of the bug, you'd think that capping > > oslo.utils<1.2.1 would be an alternative fix, but I tried installing > > older versions of oslo.utils and eventually it failed with a completely > > different error, so I think that's a dead end. > > > > [1] https://review.openstack.org/#/c/175232/ > > > > > > So this fix has merged, but keystonemiddleware has another problem -- > > the proposal bot posted a change to get the requirements up to date and > > that's failing all the -python* jobs. Looks like what's happening is > > that during the tox venv installation the oslo.messaging package is > > being updated to version 1.9.0, which is way newer than the other oslo > > packages and this is causing a test that uses pkg_resource to fail with > > a dependency issue (oslo.messaging 1.9.0 requires > > oslo.utils<1.5.0,>1.4.0 but global requirements has oslo.utils<1.2.0, > > so that's what's installed). This all appears to be related to other > > issues we've seen where the dep resolver isn't working as expected. > > > > I tried using an older pycadf (which, from the tox logs is where > > oslo.messaging is being upgraded) but it was only with a very old > > version of pycadf that things worked. > > does it make sense to make a stable/juno branch for pycadf and remove the > oslo.messaging requirement? it actually isn't a mandatory requirement and > was moved to test-requirements in 0.7.0 > > Gordon -
I think that would also work... if I have some time I'll take a look at it, or maybe someone else will get to it first. :: Brant
__________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev