Comment 5 for bug 1394453

well, it's not *that* cool. Our swiftclient gate is all messed up [1].

How is it possible we've got a hard gate failure preventing us from merging non-breaking changes to our client but the change that broke the world didn't get hit by it?

Either-way, thanks for getting on it so quickly - let me know if there's anything we can do on the swift side of the house to help out. But it feels like a process gap that warrants a post-mortem.

1. https://review.openstack.org/#/c/131238/