Public bug reported: The v2.0 API has an /extensions path that helps discoverability of extensions for v2.0 enabled for that deployment. When asking for v2.0 enabled extensions, you actually get APIs that are meant only for v3.
To recreate, just ask v2.0 for it's extensions, something like: $ curl -X GET -H "Content-Type: application/json" http://192.168.122.160:35357/v2.0/extensions Which gives you something like this: http://paste.openstack.org/show/658357/ ** Affects: keystone Importance: Undecided Status: New -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Identity (keystone). https://bugs.launchpad.net/bugs/1746798 Title: v2.0/extensions API exposes v3-only APIs Status in OpenStack Identity (keystone): New Bug description: The v2.0 API has an /extensions path that helps discoverability of extensions for v2.0 enabled for that deployment. When asking for v2.0 enabled extensions, you actually get APIs that are meant only for v3. To recreate, just ask v2.0 for it's extensions, something like: $ curl -X GET -H "Content-Type: application/json" http://192.168.122.160:35357/v2.0/extensions Which gives you something like this: http://paste.openstack.org/show/658357/ To manage notifications about this bug go to: https://bugs.launchpad.net/keystone/+bug/1746798/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : [email protected] Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
