Hi,

Dolph please see - https://github.com/openstack/tempest/blob/stable/grizzly/tools/pip-requires#L10

This could be the cause of the problem. I think that either we need to lock down the client for the stable/grizzly tempest branch or add netaddr.

What do you guys suggest?

At the moment the reviews are piling up…

Thanks

Gary

 

 

From: Dolph Mathews [mailto:dolph.mathews@gmail.com]
Sent: Wednesday, August 21, 2013 4:07 PM
To: Alan Pevec
Cc: Gary Kotton; openstack-stable-maint@lists.openstack.org

Subject: Re: [Openstack-stable-maint] Stable grizzly failures

 

 

On Wed, Aug 21, 2013 at 4:00 AM, Alan Pevec <apevec@gmail.com> wrote:

Hi Gary,

we should figure out which version of keystoneclient Tempest is using,
I could not parse that information from tempest log.
At the same time, keystone jobs are failing with ImportError: No
module named netaddr in common/jsonutils, that's a design issue with
test_keystoneclient in Keystone: checking out keystoneclient from git
master, assuming dependecies didn't change since last release, which
isn't the case since[1] was merged after 0.3.1.
Quick fix would be to release a new keystoneclient which has updated
requirements, so new deps get pulled into venv.

 

If that happens to be acceptable fix, I was intending to release a new version of keystoneclient in the next day or so anyway.

 

Besides those keystoneclient related failures, we have Glance and Heat
jobs failing and returning back to normal randomly.

Cheers,
Alan

[1] https://github.com/openstack/python-keystoneclient/commit/de72de3b809c53420d2936b619d613c4294e4329

_______________________________________________
Openstack-stable-maint mailing list
Openstack-stable-maint@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-stable-maint

 

--

 

-Dolph