Ask Your Question
0

neutron client authentication failed [closed]

asked 2013-11-27 13:20:47 -0500

arunuke gravatar image

updated 2013-11-30 23:43:08 -0500

[Edit1: Added new information below based on Dheeru's request]

[Edit 2: Clarification on Dheeru's second comment]

I am running Havana/Fedora 19 and my nova-compute reports neutron authentication failure. It indicates that the service or the endpoint are not available. I posted a request on the launchpad URL and I got a suggestion to include neutron_region_name in the nova.conf file. I included it on both the controller and the compute nodes and restarted all my services, but I am still running into the same error.

Since I am using RDO packages, I thought I'd post it it on the RDO forum to see if anyone can point me in the right direction. A copy-paste of my question from the launchpad site is attached below.

=========BEGIN COPY/PASTE===========

I am running Havana on a Fedora 19 system and I am running into some issues in nova-compute when booting an instance. I am getting a "neutron client authentication failed: Could not find Service or Region in Service Catalog" error in the nova-compute log file (note 1). However, the endpoints do exist when run from the controller node (note 2). I am also able to use the neutron client to print previously created networks and all other related information (note 3), so I am not quite sure if it's the endpoint that is causing issues. Nova.conf appears to have the right settings to indicate where the neutron is running (note 4) while the api-paste.ini file also the right information (note 5). To verify, I ran keystone commands from the compute host and I am able to see the endpoints (note 6).

It does not appear to be the issue described in https://bugs.launchpad.net/nova/+bug/1241275 since the stack traces are different. From the looks of it, in my case, there is an attempt to get the token and it fails to locate even the endpoint. Any thoughts or suggestions in this regard are greatly appreciated.

Notes:

nova-compute log:

2013-11-26 14:02:56.921 2493 ERROR nova.network.neutronv2 [req-662e2363-cdcb-495e-96c3-d9852fcfea59 None None] Neutron client authentication failed: Could not find Service or Region in Service Catalog.
2013-11-26 14:02:56.922 2493 ERROR nova.compute.manager [req-662e2363-cdcb-495e-96c3-d9852fcfea59 None None] Instance failed network setup after 1 attempt(s)
2013-11-26 14:02:56.922 2493 TRACE nova.compute.manager Traceback (most recent call last):
2013-11-26 14:02:56.922 2493 TRACE nova.compute.manager File "/usr/lib/python2.7/site-packages/nova/compute/manager.py", line 1228, in _allocate_network_async
2013-11-26 14:02:56.922 2493 TRACE nova.compute.manager dhcp_options=dhcp_options)
2013-11-26 14:02:56.922 2493 TRACE nova.compute.manager File "/usr/lib/python2.7/site-packages/nova/network/api.py", line 49, in wrapper
2013-11-26 14:02:56.922 2493 TRACE nova.compute.manager res = f(self, context, *args, **kwargs)
2013-11-26 14:02:56.922 2493 TRACE nova.compute.manager File "/usr/lib/python2.7/site-packages/nova/network/neutronv2/api.py", line 358, in allocate_for_instance
2013-11-26 14 ...
(more)
edit retag flag offensive reopen merge delete

Closed for the following reason the question is answered, right answer was accepted by dheeru
close date 2013-12-01 08:49:30.957671

Comments

Do you still have the issue ? Can you get the output of 'keystone service-list' ?

dheeru gravatar imagedheeru ( 2013-11-30 10:36:18 -0500 )edit

Hi Arun I felt too much information above and not able to co-relate. Do you see the same exception ? Also I saw mismatch in endpoint list displayed in compute and controller. Can you check is there a mismatch. Request you to start adding comments rather updating the same question. You can drop me an email with more details.

dheeru gravatar imagedheeru ( 2013-12-01 00:24:25 -0500 )edit

My bad. The mismatch in endpoints in the two outputs is because I had re-created the setup entirely. 1. I verified that the endpoint's service id and the actual service id of neutron match completely. 2. I am able to use the neutron client directly to get the network information from the compute host (using both admin/admin/admin and neutron/neutron/service credentials) 3. I will send you an email with additional details. Thanks again for your assistance.

arunuke gravatar imagearunuke ( 2013-12-01 01:01:03 -0500 )edit

Issue seems to be resolved now :). I had used neutron_admin_tenant instead of neutron_admin_tenant_name in the nova.conf file (dang). I used the debug feature and I found that the tenant name was not set which had me go back and look into the file again. Thanks a ton Dheeru for all your assistance.

arunuke gravatar imagearunuke ( 2013-12-01 01:21:02 -0500 )edit

that is cool. I will close this request now.

dheeru gravatar imagedheeru ( 2013-12-01 08:46:17 -0500 )edit

1 answer

Sort by ยป oldest newest most voted
0

answered 2013-11-30 21:22:08 -0500

dheeru gravatar image

updated 2013-12-01 08:49:05 -0500

Issue was neutron_admin_tenant_name in nova.conf. It was wrongly mentioned as neutron_admin_tenant in nova.conf. --debug option helped to troubleshoot.

edit flag offensive delete link more

Get to know Ask OpenStack

Resources for moderators

Question Tools

1 follower

Stats

Asked: 2013-11-27 13:20:47 -0500

Seen: 7,079 times

Last updated: Dec 01 '13