[openstack-dev] [All] Fixed recent gate issues

Matthew Treinish mtreinish at kortar.org
Tue Feb 18 20:04:27 UTC 2014


On Tue, Feb 18, 2014 at 08:27:16PM +0100, Alan Pevec wrote:
> Hi John,
> 
> thanks for the summary.
> I've noticed one more fall out from swiftclient update in Grenade jobs
> running on stable/havana changes e.g.
> http://logs.openstack.org/02/73402/1/check/check-grenade-dsvm/a5650ac/console.html
> ...
> 2014-02-18 13:00:02.103 | Test Swift
> 2014-02-18 13:00:02.103 | + swift --os-tenant-name=demo
> --os-username=demo --os-password=secret
> --os-auth-url=http://127.0.0.1:5000/v2.0 stat
> 2014-02-18 13:00:02.284 | Traceback (most recent call last):
> 2014-02-18 13:00:02.284 |   File "/usr/local/bin/swift", line 35, in <module>
> 2014-02-18 13:00:02.284 |     from swiftclient import Connection, HTTPException
> 2014-02-18 13:00:02.285 | ImportError: cannot import name HTTPException
> 2014-02-18 13:00:02.295 | + STATUS_SWIFT=Failed
> ...
> 
> Grenade job installs swiftclient from git master but then later due to
> python-swiftclient>=1.2,<2 requirement in Grizzly, older version 1.9.0
> is pulled from pypi and then half-installed or something, producing
> above conflict between swift CLI binary and libs.
> Solution could be to remove swiftclient cap in Grizzly, any other suggestions?

Yeah it's pip weirdness where things falls apart because of version cap. It's
basically installing bin/swift from 1.9 when it sees the version requirement
but it leaves everything in python-swiftclient namespace from master.

So I've actually been looking at this since late yesterday the conclusion we've
reached is to just skip the exercises on grizzly. Removing the version cap isn't
going to be simple on grizzly because there global requirements wasn't enforced
back in grizzly. We'd have to change the requirement for both glance, horizon,
and swift and being ~3 weeks away from eol for grizzly I don't think we should
mess with that. This failure is only an issue with cli swiftclient on grizzly
(and one swift functional test) which as it sits now is just the devstack
exercises on grenade. So if we just don't run those exercises on the grizzly
side of a grenade run there shouldn't be an issue. I've got 2 patches to do
this here:

https://review.openstack.org/#/c/74419/

https://review.openstack.org/#/c/74451/


-Matt Treinish



More information about the OpenStack-dev mailing list