Auto detect of auth_type broken

[Terry Howe]

The auto detection of auth type is broken because --os-auth-type is defaulted to os_password, so it never goes through the code to make the decision.

[Andrey Pavlov (apavlov-e)]

after devstack installed I get error from openstack client -

. ~/devstack/accrc/admin/admin
(0):~/$ openstack endpoint list
ERROR: openstack The resource could not be found. (HTTP 404)
(1):~/$ openstack --os-identity-api-version=3 endpoint list
ERROR: openstack The resource could not be found. (HTTP 404)

debug output contains
DEBUG: openstackclient.common.clientmanager Using parameters {'username': 'admin', 'tenant_name': 'admin', 'password': 'password', 'auth_url': 'http://192.168.137.21:35357'}
DEBUG: openstackclient.common.clientmanager Get auth_ref
DEBUG: keystoneclient.auth.identity.v2 Making authentication request to http://192.168.137.21:35357/tokens
INFO: requests.packages.urllib3.connectionpool Starting new HTTP connection (1): 192.168.137.21
DEBUG: requests.packages.urllib3.connectionpool "POST /tokens HTTP/1.1" 404 93
DEBUG: keystoneclient.session Request returned failure status: 404

[Andrey Pavlov (apavlov-e)]

also it works with -
openstack --os-auth-url=$OS_AUTH_URL/ endpoint list

adn with -
openstack --os-auth-url=$OS_AUTH_URL/v2.0 endpoint list

[Guilherme Correa (gsc)]

were you able to get a resolution for your problem? I am having a similar oissue when installing my compute node. Mine is failing when stack.sh tries to create the alt_demo project.

openstack --os-url=http://:5000/v3 --os-identity-api-version=3 project create alt_demo --domain=default --or-show -f value -c id

This steps fails with error 404.

2015-10-20 21:45:47.287 | The resource could not be found. (HTTP 404)

Get auth_ref Making authentication request to http://:35357/tokens Starting new HTTP connection (1): "POST /tokens HTTP/1.1" 404 93 Request returned failure status: 404 The resource could not be found. (HTTP 404)

I had to source the admin file from the controller node.

[Guilherme Correa (gsc)]

Andrey,

It seems that your bug direct me to find a solution for my bug.

I found what was causing the error. When I did source the controller node admin file (*), the variable OS_AUTH_TYPE got set with value of v2password and somehow it was breaking the logic used to decide the type of auth to use to access the controller node.

Once I unset that variable the command worked.

Check if this variable is set on your environment.

(*) had to do it to set some variables to have the compute node accessing the controller node correctly