[PKG-Openstack-devel] Keystone v3 endpoint missing

[Thomas Goirand]

On 06/08/2016 04:17 PM, Turbo Fredriksson wrote:
> I think this looks wrong:
> 
> ----- s n i p -----
> bladeA01b:~# openstack endpoint list
> +----------------------------------+-----------+--------------+--------------+---------+-----------+----------------------------+
> | ID                               | Region    | Service Name | Service Type | Enabled | Interface | URL                        |
> +----------------------------------+-----------+--------------+--------------+---------+-----------+----------------------------+
> | 815c917fd6a648dd95558e471608e7c1 | regionOne | keystone     | identity     | True    | public    | http://10.0.4.1:5000/v2.0  |
> | 8b046355ab744f6780e7fc5abff9de67 | regionOne | keystone     | identity     | True    | admin     | http://10.0.4.1:35357/v2.0 |
> | e49d00a71b1e4cbaaf8b328941bb2479 | regionOne | keystone     | identity     | True    | internal  | http://10.0.4.1:5000/v2.0  |
> +----------------------------------+-----------+--------------+--------------+---------+-----------+----------------------------+
> bladeA01b:~# env | grep ^OS | egrep 'AUTH|VERSION'
> OS_IMAGE_API_VERSION=2
> OS_IDENTITY_API_VERSION=3
> OS_AUTH_URL=http://10.0.4.1:35357/v3
> ----- s n i p -----
> 
> Why is there no "../v3" endpoint, and why is it working when
> there is none, and my AUTH_URL is "../v3"??
> 
> I'm really confused! This is at least the third time I'm
> reinstalling keystone today (the first times I couldn't get
> v3 to work and now it suddenly does).

That's confusing, but it works. It's like that otherwise not all Tempest
tests are passing. Even with a /v2.0, you can use the v3 anyway.

> Btw, is there something wrong with v3 auth in Jessie? After
> the upgrade to testing (and at least one purge+install of
> keystone) it now works, while earlier it borked all over the
> place.

Nothing wrong that I know of.

Cheers,

Thomas Goirand (zigo)