Ask Your Question
0

Error - "Unable to find authentication token in headers" when run "nova image-list on a new install env

asked 2015-10-20 09:53:05 -0600

Allen Liu gravatar image

updated 2015-10-21 01:13:13 -0600

I just tried to set up a minimum environment with a control node, a network node and a compute node by following the document "openstack-install-guide-kilo.pdf". I went through setting up keystone, glance and compute. At the end of Adding Compute Node section, it verifies the install. The commands "nova service-list", "nova endpoints" had good normal results.

But "nova image-list" has following error:

$ nova image-list
ERROR (ClientException): The server has either erred or is incapable of performing the requested operation. (HTTP 500) (Request-ID: req-2c4cd3c7-da8d-480d-949d-1a54f51ec994)
The error "HTTP 500" is kind of general error from http server.

From glance-registry.log, it has following error msg:

2015-10-19 20:08:14.976 32745 WARNING keystonemiddleware.auth_token [-] Identity response: {"error": {"message": "The request you have made requires authentication.", "code": 401, "title": "Unauthorized"}}
2015-10-19 20:08:14.997 32745 WARNING keystonemiddleware.auth_token [-] Identity response: {"error": {"message": "The request you have made requires authentication.", "code": 401, "title": "Unauthorized"}}
2015-10-19 20:08:14.997 32745 WARNING keystonemiddleware.auth_token [-] Authorization failed for token
2015-10-19 20:08:14.998 32745 INFO eventlet.wsgi.server [-] 127.0.0.1 - - [19/Oct/2015 20:08:14] "GET /images/detail?is_public=none&limit=20 HTTP/1.1" 401 187 0.063297
2015-10-19 20:08:15.000 32745 WARNING keystonemiddleware.auth_token [-] Unable to find authentication token in headers
2015-10-19 20:08:15.001 32745 INFO eventlet.wsgi.server [-] 127.0.0.1 - - [19/Oct/2015 20:08:15] "GET /images/detail?is_public=none&limit=20 HTTP/1.1" 401 187 0.000781

I searched the forum, I knew there is a post "nova image-list returns 500 error", I tried the steps listed in that post but it didn't fix my issue. I have double, triple checked the configuration in nova.conf, glance-api.conf, glance-registry.conf. restarted all nova, glance services, but the error is still there. Can anyone tell what I could do to investigate it?

Some other info is as below.

Thanks,

Allen

nova.conf on control node:

#cat /etc/nova/nova.conf

[DEFAULT]

dhcpbridge_flagfile=/etc/nova/nova.conf

dhcpbridge=/usr/bin/nova-dhcpbridge

log_dir=/var/log/nova

state_path=/var/lib/nova

lock_path=/var/lock/nova

force_dhcp_release=True

libvirt_use_virtio_for_bridges=True

verbose=True

ec2_private_dns_show_ip=True

api_paste_config=/etc/nova/api-paste.ini

enabled_apis=ec2,osapi_compute,metadata

rpc_backend = rabbit

auth_strategy = keystone

my_ip = 10.6.117.173

vncserver_listen = 10.6.117.173

vncserver_proxyclient_address = 10.6.117.173

[oslo_messaging_rabbit]

rabbit_host=fbdl4

rabbit_userid=openstack

rabbit_password=abc123

[database]

connection = mysql://nova:abc123@fbdl4/nova

[keystone_authtoken]

auth_uri = http://fbdl4:5000

auth_url = http://fbdl4:35357

auth_plugin = password

project_domain_id = default

user_domain_id = default

project_name = service

username = nova

password = abc123

[glance]

host = fbdl4

[oslo_concurrency]

lock_path = /var/lib/nova/tmp

Add glance-registry.conf:

[DEFAULT]
# Show more verbose log output (sets INFO log level output)

#verbose = False
verbose = True

# Show debugging output in logs (sets DEBUG log level output)
#debug = False

# Address to bind the registry server
bind_host = 0.0.0.0

# Port the bind the registry server to
bind_port = 9191

# Log to this file. Make sure you do not set the same log file for both ...
(more)
edit retag flag offensive close merge delete

Comments

Sorry, don't know how to format the post.

Allen Liu gravatar imageAllen Liu ( 2015-10-20 01:09:39 -0600 )edit

I wonder where the 127.0.0.1 in your debug output comes from. Not very usual, especially if you have a multinode config. Could this be related to your problem?

nova image-list is really a Glance command. It seems your Nova commands work, but Glance doesn't. This is where you need to investigate.

Bernd Bausch gravatar imageBernd Bausch ( 2015-10-20 19:19:31 -0600 )edit

The 127.0.0.1 message was from glance-registry.log. All Glance, keystone, and Nova-control are on same node. "glance image-list" and "nova service-list" ran OK, and both didn't generate any message in glance-registry.log.

Seems Glance does not authenticate Nova ? Where should I investigate ?

Allen Liu gravatar imageAllen Liu ( 2015-10-21 01:01:04 -0600 )edit

Added glance-registry.conf in my original post.

Allen Liu gravatar imageAllen Liu ( 2015-10-21 01:08:35 -0600 )edit

1 answer

Sort by ยป oldest newest most voted
0

answered 2015-10-21 12:34:33 -0600

Allen Liu gravatar image

Fixed: A typo in glance-registry.conf: should be "password= ..." instead of "Password=...."

edit flag offensive delete link more

Your Answer

Please start posting anonymously - your entry will be published after you log in or create a new account.

Add Answer

Get to know Ask OpenStack

Resources for moderators

Question Tools

1 follower

Stats

Asked: 2015-10-19 23:55:40 -0600

Seen: 940 times

Last updated: Oct 21 '15