warning: bypassing authentication using a token & endpoint(authentication credentials are being ignored)
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
python-keystoneclient |
Invalid
|
Low
|
Unassigned | ||
python-openstackclient |
Confirmed
|
Low
|
Unassigned |
Bug Description
warning: bypassing authentication using a token & endpoint(
'NoneType' object has no attribute 'has_service_
This is the ERROR MESSAGE i get during configuring of keystone identity service after successful:Install the Identity Service-->Define users, tenants, and role-->Define services and API endpoints---> verifying the identity Service installation(ERROR HERE)
#cat>keystonerc
export OS_USERNAME=admin
export OS_PASSWORD=
export OS_TENANT_
export OS_AUTH_URL=http://
NOTE: controller is my host name configured in /etc/hosts
and exported it using
# source keystonerc
# keystone token-get
warning: bypassing authentication using a token & endpoint(
'NoneType' object has no attribute 'has_service_
i also done this below step before creating user "admin" and tenant "admin" and many times again after error.
# unset OS_SERVICE_TOKEN OS_SERVICE_ENDPOINT
I am using ubuntu 12.04 LTS for configuring openstack over Virtualbox.
somebody please help on my problem.
Thank you in advance.
description: | updated |
description: | updated |
description: | updated |
description: | updated |
description: | updated |
description: | updated |
tags: | added: documentation |
Changed in python-keystoneclient: | |
status: | New → Fix Released |
Changed in python-keystoneclient: | |
status: | Fix Released → Triaged |
The warning line is just that - a warning. You must have a token and endpoint in your environment (there are deprecated environment variables names that are still supported that could be in use). However, in the case of token-get, using a token & endpoint is actually the cause of "'NoneType' object has no attribute 'has_service_ catalog' " (without authenticating, you don't have a catalog, and therefore can't get a token, as expected).
The last error message here ('NoneType' object has no attribute 'has_service_ catalog' ) could definitely be improved, but this sounds like expected behavior. The client *could* also attempt to actually exchange a token for another with token-get against the specified endpoint, but I'm not sure there's a valid use case for that behavior.