2014-02-23 10:52 GMT+01:00 Gary Kotton gkot...@vmware.com:
It looks like this does not solve the issue.
Yeah https://review.openstack.org/74451 doesn't solve the issue
completely, we have
SKIP_EXERCISES=boot_from_volume,bundle,client-env,euca,swift,client-args
but failure is now in Grenade's
https://review.openstack.org/74451 doesn't solve the issue completely, we have
SKIP_EXERCISES=boot_from_volume,bundle,client-env,euca,swift,client-args
but failure is now in Grenade's Javelin script:
+ swift upload javelin /etc/hosts
...(same Traceback)...
[ERROR]
On 2/19/14 10:31 PM, Alan Pevec ape...@gmail.com wrote:
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
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
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 | +
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
...
As many of you surely noticed, we had some significant significant
gate issues in the last day. It's fixed now, and I've got the details below.
The root cause of the issue was a lack of proper testing in python-
swiftclient. We've made some improvements here in the last few hours,
but improving
On 02/14/2014 02:15 PM, John Dickinson wrote:
As many of you surely noticed, we had some significant significant
gate issues in the last day. It's fixed now, and I've got the
details below.
The root cause of the issue was a lack of proper testing in
python- swiftclient. We've made some
