keystone v2.0 doesn't work when v3 in the catalog endpoint

Bug #1713616 reported by Sam Morrison on 2017-08-29
This bug affects 1 person
Affects Status Importance Assigned to Milestone

Bug Description

We recently changed the identity endpoint that is advertised in our catalog from




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 to instantiate a client however it doesn't work.

We are using the latest version available from pip:


  File "/opt/tempest/local/lib/python2.7/site-packages/keystoneclient/v2_0/", line 50, in list
    return self._list("/OS-KSADM/roles", "roles")
  File "/opt/tempest/local/lib/python2.7/site-packages/keystoneclient/", line 125, in _list
    resp, body = self.client.get(url, **kwargs)
  File "/opt/tempest/local/lib/python2.7/site-packages/keystoneauth1/", line 216, in get
    return self.request(url, 'GET', **kwargs)
  File "/opt/tempest/local/lib/python2.7/site-packages/keystoneauth1/", line 373, in request
    resp = super(LegacyJsonAdapter, self).request(*args, **kwargs)
  File "/opt/tempest/local/lib/python2.7/site-packages/keystoneauth1/", line 141, in request
    return self.session.request(url, method, **kwargs)
  File "/opt/tempest/local/lib/python2.7/site-packages/positional/", line 101, in inner
    return wrapped(*args, **kwargs)
  File "/opt/tempest/local/lib/python2.7/site-packages/keystoneauth1/", line 492, in request
    raise exceptions.EndpointNotFound()

Lance Bragstad (lbragstad) wrote :

This could be related to keystoneauth version discovery. Adding a developer who is more familiar with that flow.

Lance Bragstad (lbragstad) wrote :

This exception is also coming from keystoneauth, not python-keystoneclient (python-keystoneclient invokes keystonauth). Updating the affected projects accordingly.

Changed in python-keystoneclient:
status: New → Invalid
Eric Fried (efried) wrote :

This may be a dup of [1], which was fixed in ksa 3.2.0 via [2]


You can confirm by removing the trailing slash from your catalog entry; or just upgrade to 3.2.0 and see if the problem disappears.

Lance Bragstad (lbragstad) wrote :

I ran this issue by a couple people who are more familiar with keystoneauth [0].

There was an issue with keystoneauth 3.1.0 with version discovery. The suggestions is to either upgrade to 3.2.0 or try removing the trailing slash from the endpoint. More context from that specific issue can be found in .


Changed in keystoneauth:
status: New → Incomplete
Launchpad Janitor (janitor) wrote :

[Expired for keystoneauth because there has been no activity for 60 days.]

Changed in keystoneauth:
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers