Open Stack

Hi.

First - unskip proposed https://review.openstack.org/#/c/49589/
   but I'm worried that it will suffer from https://bugs.launchpad.net/neutron/+bug/1234181

Second - python-keyring issue seems already fixed in keyring>=2.1
   as per https://bitbucket.org/kang/python-keyring-lib/issue/115/error-root-could-not-find-any-typelib-for#comment-6139490 
   so we can continue with unpinning after that - https://bugs.launchpad.net/devstack/+bug/1217120

----- Original Message -----
> From: "Thierry Carrez" <thierry at openstack.org>
> To: "Pavel Sedlak" <psedlak at redhat.com>
> Cc: "openstack-stable-maint" <openstack-stable-maint at lists.openstack.org>, "Alan Pevec" <apevec at gmail.com>, "David
> Kranz" <dkranz at redhat.com>
> Sent: Thursday, September 26, 2013 11:53:22 AM
> Subject: Re: [Openstack-stable-maint] Stable grizzly failures
> 
> Thierry Carrez wrote:
> > Pavel Sedlak wrote:
> >> Yes we should be ok to remove those skips with keyring < 2.0.
> >>
> >> But to stop thinking about it, we should first at least
> >> get https://bugs.launchpad.net/ubuntu/+source/python-keyring/+bug/1197988
> >> moving,
> >> but I can't re-open it. So who can?
> > 
> > You should probably file a separate bug about the reintroduction of the
> > same issue in 2.0, referencing the original bug. That's better than
> > reopening a but that was (correctly) closed.
> > 
> >> Also I've proposed backport of complete cli-output logging also to
> >> tempest-stable/grizly https://review.openstack.org/#/c/46485/.
> >> I would suggest that un-skip should better happen after that, so we don't
> >> find ourself in the dark again.
> > 
> > OK, let's get some tempest eyes on this one...
> 
> That change was merged... If you don't see any other obstacle, please
> push a change to unskip the tests... would be great to have that in
> before we actually do 2013.1.4.
> 
> --
> Thierry Carrez (ttx)
> 

-- 
Pavel Sedlák <psedlak at redhat.com>
 OpenStack Quality Engineer
 Red Hat Czech / BRQ
 irc: psedlak
 phone: +420532294659 | (82) 62659