keystone v2.0 doesn't work when v3 in the catalog endpoint
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
keystoneauth |
Expired
|
Undecided
|
Unassigned | ||
python-keystoneclient |
Invalid
|
Undecided
|
Unassigned |
Bug Description
We recently changed the identity endpoint that is advertised in our catalog from
to
Users using all the clients (nova/cinder etc.) all still work using a v2.0 or a v3 OS_AUTH_URL config option.
The issue is the keystone client library no longer works, we get the error at the bottom of the page.
We are following the docs at https:/
We are using the latest version available from pip:
keystoneauth1=
python-
File "/opt/tempest/
return self._list(
File "/opt/tempest/
resp, body = self.client.
File "/opt/tempest/
return self.request(url, 'GET', **kwargs)
File "/opt/tempest/
resp = super(LegacyJso
File "/opt/tempest/
return self.session.
File "/opt/tempest/
return wrapped(*args, **kwargs)
File "/opt/tempest/
raise exceptions.
This could be related to keystoneauth version discovery. Adding a developer who is more familiar with that flow.