Can someone please capture how this bug affects the Ubunty python-keystoneclient package and how to reproduce with whats in the archive (saucy or trusty)? The original trace appears to implicate non-Ubuntu stuff installed by devstack (pip installed python-keyring, devstack installed python-keystoneclient). This looks more like a python-keyring or devstack issue?
Can someone please capture how this bug affects the Ubunty python- keystoneclient package and how to reproduce with whats in the archive (saucy or trusty)? The original trace appears to implicate non-Ubuntu stuff installed by devstack (pip installed python-keyring, devstack installed python- keystoneclient) . This looks more like a python-keyring or devstack issue?