13 Sep
2013
13 Sep
'13
11:22 p.m.
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... -- Thierry Carrez (ttx)