Glance image-create returns C (HTTP 500)

asked 2014-03-18 13:27:08 -0600

pratik gravatar image

I am trying various solutions for this error..but nothing is working...

getting Glance image-create returns HTTPInternalServerError (HTTP 500) when i run galnce image-list i am new to opsnstack and i m following havana installtion guide...installed and configured keystone and then glance howver finding trouble in verifying glance...

edit retag flag offensive close merge delete


please read and post tail /var/log/glance/registry.log and tail /var/log/glance/api.log

May be a error on the db creation!

New-stack gravatar imageNew-stack ( 2014-05-05 09:20:48 -0600 )edit

2 answers

Sort by ยป oldest newest most voted

answered 2014-03-18 18:53:33 -0600

You need to authenticate to OpenStack first, did you do that at the command line ?

in the Dashboard nder your Openstack project go to the Access and Security Option on the left menu, then to API's Access, you will see at the top Download Openstack RC file, this is a small script that when you run it will allow you to login to the cloud.

image description

Go ahead and download it, and run it and login

$ source <name of="" rc="" file="">

Now if you do a glance image-list you will see ...

image description

edit flag offensive delete link more

answered 2014-04-28 10:59:18 -0600

ecerulm gravatar image

In general, you should check /var/log/glance/*log for errors.

You could also check that the glance-api and glance-registry are up and running, for example sudo netstat -putona to verify that ports 9292 and 9191 are open. If, for example, you find that glance-registry is not up and running, you could scan the syslog or dmesg to find why.

In my case I could see that the glance-registry was not starting up correctly dmesg|grep glance

[12401.085246] init: glance-registry main process (10687) terminated with status 1
[12401.085265] init: glance-registry main process ended, respawning
[12401.241480] init: glance-registry main process (10692) terminated with status 1
[12401.241496] init: glance-registry respawning too fast, stopped

The ultimate reason was the permissions of the /var/log/glance/*.log. The glance-registry services is started as the glance user and if that user cannot write to the log file the process will die.

In my case the registry.log was owned by the root user. The solution was easy

sudo bash -c 'rm /var/log/glance/*'
sudo service glance-registry restart
sudo service glance-api restart
edit flag offensive delete link more

Get to know Ask OpenStack

Resources for moderators

Question Tools

1 follower


Asked: 2014-03-18 13:27:08 -0600

Seen: 1,069 times

Last updated: Apr 28 '14