openstack/python-troveclient
Code Issues Proposed changes

Fix token response mock

Browse Source 
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: Iea77ef54585d0b3480369e9f5df629e3f46f7e3b
This commit is contained in:
Lance Bragstad
2017-07-26 13:18:47 +00:00
parent 555ba5ed69
commit 47ad24a358
1 changed files with 1 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
troveclient/tests/test_shell.py
View File

@@ -74,7 +74,7 @@ class ShellTest(testtools.TestCase):
v2_auth_response = json.dumps({ v2_auth_response = json.dumps({
"access": { "access": {
"token": { "token": {
"expires_at": "2020-01-01T00:00:10.000123Z", "expires": "2020-01-01T00:00:10.000123Z",
"id": 'fakeToken', "id": 'fakeToken',
"tenant": { "tenant": {
"id": uuid.uuid4().hex "id": uuid.uuid4().hex