Ask Your Question

liberty glance image-create returns http 503 error [closed]

asked 2015-12-07 22:00:34 -0500

recital gravatar image

updated 2015-12-07 22:22:36 -0500

I am a beginner in openstack and trying to install as instructed in liberty release using centos 7. My problem occured when glance image-create or image-list. The error log is following.

"503 service unavailable: the server is currently unavailable. please try again at a later time. (HTTP 503)"

At the first time, I miss-configured [keystone_authtoken] in glance-api.conf and glance-registry.conf. I fixed it by changing auth_uri to auth_url. Before fixing it, the error returned http 500 error.

I restarted the services.

openstack service list returns glance and keystone.

openstack user list gives admin, glance, demo.

openstack endpoint gives the public, internal, admin url's for keystone and glance.

Pls, somebody help me.

the glance api.log is following.

2015-12-08 12:27:20.220 3132 ERROR keystonemiddleware.auth_token [-] Bad response code while validating token: 400

2015-12-08 12:27:20.253 3132 WARNING keystonemiddleware.auth_token [-] Identity response: {"error": {"message": "Expecting to find id or name in user - the server could not comply with the request since it is either malformed or otherwise incorrect. The client is assumed to be in error.", "code": 400, "title": "Bad Request"}}

2015-12-08 12:27:20.253 3132 CRITICAL keystonemiddleware.auth_token [-] Unable to validate token: Failed to fetch token data from identity server

2015-12-08 12:27:20.256 3132 INFO eventlet.wsgi.server [-] - - [08/Dec/2015 12:27:20] "GET /v2/images?limit=20&sort_key=name&sort_dir=asc HTTP/1.1" 503 370 1.965929

glance registry.log is following.

2015-12-08 12:22:35.966 1275 INFO glance.common.wsgi [-] Removed dead child 3058

2015-12-08 12:22:35.970 1275 INFO glance.common.wsgi [-] Started child 15944

2015-12-08 12:22:36.005 15944 INFO eventlet.wsgi.server [-] (15944) wsgi starting up on

2015-12-08 12:22:36.006 15944 INFO eventlet.wsgi.server [-] (15944) wsgi exited, is_accepting=True

2015-12-08 12:22:36.007 15944 INFO glance.common.wsgi [-] Child 15944 exiting normally

2015-12-08 12:23:00.546 1276 INFO glance.common.wsgi [-] Starting 2 workers

2015-12-08 12:23:00.550 1276 INFO glance.common.wsgi [-] Started child 3088

2015-12-08 12:23:00.554 1276 INFO glance.common.wsgi [-] Started child 3089

2015-12-08 12:23:00.557 3088 INFO eventlet.wsgi.server [-] (3088) wsgi starting up on

2015-12-08 12:23:00.565 3089 INFO eventlet.wsgi.server [-] (3089) wsgi starting up on

The --debug option result of glance image-list is following.

[root@controller ~]# glance --debug image-list

curl -g -i -X GET -H 'Accept-Encoding: gzip, deflate' -H 'Accept: /' -H 'User-Agent: python-glanceclient' -H 'Connection: keep-alive' -H 'X-Auth-Token: {SHA1}5633bb685565b6a6d9fe85f9dc602aff8588c8f4' -H 'Content-Type: application/octet-stream' http://controller:9292/v2/images?limit=20&sort_key=name&sort_dir=asc (http://controller:9292/v2/images?limi...)

Request returned failure status 503.

edit retag flag offensive reopen merge delete

Closed for the following reason the question is answered, right answer was accepted by recital
close date 2015-12-07 23:32:28.407247


"... I fixed it by changing auth_uri to auth_url..." ---- Hi, I am getting the same error. My glance-api.conf file has the following configuration [keystone_authtoken] auth_uri = http://controller:5000 auth_url = http://controller:35357 Do I need to change both of them ?

pjb gravatar imagepjb ( 2015-12-20 09:44:56 -0500 )edit

1 answer

Sort by ยป oldest newest most voted

answered 2015-12-07 23:31:47 -0500

recital gravatar image

I solved this issue. I used "user-name" instead of "username" in glance-api.conf and glance-registry.conf. I changed it because when I used "username", the api.log gave me the warning saying "username" is deprecated and you should use "user-name" instead. After ignoring the warning and change it with "username' as it used to be, I could get image-create and image-list well. Sorry for my mistake, but openstack should change the warning in api.log of glance.

edit flag offensive delete link more

Get to know Ask OpenStack

Resources for moderators

Question Tools



Asked: 2015-12-07 22:00:34 -0500

Seen: 6,195 times

Last updated: Dec 07 '15