The unit tests mock tokens from keystoneauth. One of the responses
being returned from a mocked keystoneauth method was returning a v2.0
token that didn't have the right expiration attribute of a v2.0
token. This was caught by keystoneauth 3.0.1, which underwent a
significant refactor and added a bunch of new functionality for
version discovery. Keystoneauth was expecting `expires` to be
in the token but instead the mock was using `expires_at`, which isn't
a valid v2.0 token attribute.
Reviewed: https:/ /review. openstack. org/487417 /git.openstack. org/cgit/ openstack/ python- troveclient/ commit/ ?id=47ad24a3581 04d41b915f25cdd 5a17d915c6ee75
Committed: https:/
Submitter: Jenkins
Branch: master
commit 47ad24a358104d4 1b915f25cdd5a17 d915c6ee75
Author: Lance Bragstad <email address hidden>
Date: Wed Jul 26 13:18:47 2017 +0000
Fix token response mock
The unit tests mock tokens from keystoneauth. One of the responses
being returned from a mocked keystoneauth method was returning a v2.0
token that didn't have the right expiration attribute of a v2.0
token. This was caught by keystoneauth 3.0.1, which underwent a
significant refactor and added a bunch of new functionality for
version discovery. Keystoneauth was expecting `expires` to be
in the token but instead the mock was using `expires_at`, which isn't
a valid v2.0 token attribute.
Closes-Bug: 1706538
Change-Id: Iea77ef54585d0b 3480369e9f5df62 9e3f46f7e3b