Comment 1 for bug 1706538

I've proposed a patch to python-troveclient to adjust a token mock that was using the wrong expiration attribute for v2.0 tokens. It just happen to be keystoneauth that stumbled across the error because it expects `expires` to be in the token reference. There was a lot of shuffling in the last release of keystoneauth, so a shift in logic, or how keystoneauth is invoked probably triggered this.

https://github.com/openstack/python-troveclient/blob/555ba5ed690027088358288c9b0252d5a58bdc0d/troveclient/tests/test_shell.py#L77