Hi, sorry I missed this. 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? 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. ----- Original Message -----
From: "Thierry Carrez" <thierry@openstack.org> To: "Alan Pevec" <apevec@gmail.com> Cc: "openstack-stable-maint" <openstack-stable-maint@lists.openstack.org>, "Pavel Sedlák" <psedlak@redhat.com>, "David Kranz" <dkranz@redhat.com> Sent: Tuesday, September 10, 2013 11:09:49 AM Subject: Re: [Openstack-stable-maint] Stable grizzly failures
Alan Pevec wrote:
2013/8/29 Thierry Carrez <thierry@openstack.org>:
Can we mark https://bugs.launchpad.net/devstack/+bug/1193164 fixcomitted too ?
Please note https://bugs.launchpad.net/devstack/+bug/1217120 where it wants to unpin keyring as soon as 1193164 is fixed but fix for 1193164 was pinning, so we're full circle :)
1217120 should probably depend on a fix in keyring, i.e. reopen 1197988 based on https://bugs.launchpad.net/ubuntu/+source/python-keyring/+bug/1197988/commen...
Is there anything else we need to do before we can reenable the tests that were temporarily disabled at: https://github.com/openstack/tempest/commit/27e8547c31f15708b3ff143a62eb9674... ?
AFAICT keystone cli tests can be re-enabled now, but I'd like to hear from Pavel first.
Pavel: any news ? I would really like to reenable the tests before I stop thinking about this issue to focus on havana release :)
-- Thierry Carrez (ttx)
-- Pavel Sedlák <psedlak@redhat.com> irc: psedlak