Ask Your Question

Mitaka Nova Create VM failed caused by get glance image failed

asked 2016-09-05 10:19:32 -0600

JackLin gravatar image

Hi, everyone. I have encountered a situation which is a little bit different from the questions on the board.

I installed Mitaka on three physical server

Controller Node (internal network)

Network Node

Compute1 Node

I have already install keystone,glance,nova,network, and horizon. All the service are running well now. The image created and uploaded to glance well, sub-net create well. I can list my image by using nova or glance api well. But, I got error when I want to boot my VM by nova-client.

  • list the image using nova and glance api

View post on
  • boot the VM by nova-client

View post on
  • openstack server show test13

View post on

Below is the log info


/var/log/glance/ registry.log

View post on


View post on

openstack endpoint

View post on



nova-compute.log (I got lots of error here)


View post on


View post on


View post on




View post on


View post on

any idea? Thx very much! Sorry for the inconvenience of the present of the picture.

edit retag flag offensive close merge delete

2 answers

Sort by ยป oldest newest most voted

answered 2016-09-06 22:34:32 -0600

I see you glance is looking for the hostname "controller"..... Check your /etc/hosts file to ensure this is setup and pingable on your nova host to your glance host.

ping controller.

should start working after this....

edit flag offensive delete link more

answered 2016-09-07 08:08:30 -0600

JackLin gravatar image

Thank you for your response! I have solved the problem today, It's not a conspicuous error.

First of all, I can ping my controller from compute node successfully, and all the settings are right. After reading the nova-compute.log again and again, I found that neutron service get the similar error as glance. I started to think that the error was not in the glance but in basic settings. Finally, the error was in rabbitmq.service and firewall. It seems that firewall will make rabbitmq.service failed. It's interesting that though I closed the firewall, started the rabbitmq.service successfully in the beginning, restart the firewall, and checked the rabbitmq.service working well again. As firewall keep working, the rabbitmq.service failed even if its status was running. So, I closed my firewall, restart the rabbitmq.service, and didn't restart the firewall. The result was great, I successfully create the VM!

edit flag offensive delete link more

Get to know Ask OpenStack

Resources for moderators

Question Tools

1 follower


Asked: 2016-09-05 10:18:12 -0600

Seen: 172 times

Last updated: Sep 06 '16