Ask Your Question
0

I am Configuring the OpenStack services to use the Keystone V3 API. When I hit the v3 url it is working fine but when try to access v3 apis using simplet token secret it says "V3 endpoints must have been created in OpenStack" [closed]

asked 2015-12-21 07:07:37 -0500

rohit_j.waghmare@ymail.com gravatar image

I am Configuring the OpenStack services to use the Keystone V3 API. Updated the config files as per the requirements and when I hit the v3 url it is working fine but when try to access v3 apis using simplet token secret it says "V3 endpoints [http://myipaddress:5000/v3, internal] [http://myipaddress:5000/v3, public] must have been created in OpenStack" and also it says "The value of SIMPLE_TOKEN_SECRET must be correct for the host my_ip_address" where as token values are correct.

Details: - Checking that the parameter SIMPLE_TOKEN_SECRET can be used to authenticate with my_ip_address - Status: Failed - Message text: The value of SIMPLE_TOKEN_SECRET must be correct for the host my_ip_address

ERROR: 401 - Message: The request you have made requires authentication. SIMPLE_TOKEN_SECRET is not valid - User response: Check that the value of the parameter SIMPLE_TOKEN_SECRET is correct

  • Checking that the API for endpoints is available and required entries exist
    • Status: Failed
    • Message text: V3 endpoints [http://my_ip_address:5000/v3, internal] [http://my_ip_address:5000/v3, public] must have been created in OpenStack ERROR: Required items not found: [http://my_ip_address:5000/v3, internal] [http://my_ip_address:5000/v3, public]
    • User response: Check that the ICM configure script has been run on the OpenStack instance. See: https://www-03preprod.ibm.com/support/knowledgecenter/SS4KMC_2.5.0/com.ibm.ico.doc_2.5/t_config_icm.html (https://www-03preprod.ibm.com/support...)
edit retag flag offensive reopen merge delete

Closed for the following reason the question is answered, right answer was accepted by Bipin
close date 2015-12-23 22:31:23.423586

Comments

I am unable to give you a answer to this as I haven't started using keystone v3 ... but what i can suggest you is run this 'nova --debug list &> temp'... This will store the output to temp file and then see when nova asks keystone for token what does is send in the curl command ? ..

Prateek K gravatar imagePrateek K ( 2015-12-22 00:00:32 -0500 )edit

It sends v3 url for authentication and successfully receives x-auth token. REQ: curl -g -i -X GET http://my_hostame:5000/v3 -H "Accept: application/json" -H "User-Agent: python-keystoneclient".

rohit_j.waghmare@ymail.com gravatar imagerohit_j.waghmare@ymail.com ( 2015-12-22 00:28:17 -0500 )edit

Hmm here also its hiding everything... Hm do one thing enable debug and verbose mode in the config files of nova keystone ...restart the services and see the logs then if you get any more info in the logs. The idea is to see how keystone is called by nova and what has changed

Prateek K gravatar imagePrateek K ( 2015-12-22 01:13:03 -0500 )edit

Somewhere in the file of nova-api.log I found, " . . 2015-12-22 13:05:04.094 28486 WARNING oslo_config.cfg [-] Option "username" from group "keystone_authtoken" is deprecated. Use option "username" from group "keystone_authtoken". 2015-12-22 13:05:04.098 28486 INFO nova.api.openstack [-]

rohit_j.waghmare@ymail.com gravatar imagerohit_j.waghmare@ymail.com ( 2015-12-22 01:51:49 -0500 )edit

2015-12-22 13:05:04.098 28486 INFO nova.api.openstack [-] V3 API has been disabled by configuration

rohit_j.waghmare@ymail.com gravatar imagerohit_j.waghmare@ymail.com ( 2015-12-22 01:52:32 -0500 )edit

1 answer

Sort by ยป oldest newest most voted
0

answered 2015-12-22 06:12:30 -0500

Prateek K gravatar image

in the log it clearly says multiple times that the v3 version of keystone has been disabled in configuration.

I assume you are on Kilo version so can you check the following things:-

  • Do a openstack endpoint-list and see in the URL it is set to v3 or v2 ?
  • http://docs.openstack.org/kilo/instal... --- Just cross-verify your nova.conf configuration with this link and see if everything is correct

I think it can get solved by this... Still if it doesn't work let me know so that we can go deeper, at-least by doing this we will be sure that nova is using v3 or v2

edit flag offensive delete link more

Comments

Yes, endpoints were not configured for V3. I had to create them manually using openstack endpoint create. Thanks for help.

rohit_j.waghmare@ymail.com gravatar imagerohit_j.waghmare@ymail.com ( 2015-12-23 02:30:44 -0500 )edit

Get to know Ask OpenStack

Resources for moderators

Question Tools

1 follower

Stats

Asked: 2015-12-21 07:07:37 -0500

Seen: 339 times

Last updated: Dec 22 '15