Ask Your Question

Instance going into ERROR state as soon as I give nova boot.

asked 2015-04-27 08:04:52 -0500

Zishan gravatar image

updated 2015-04-27 12:21:46 -0500

dbaxps gravatar image

I am using Ubuntu 12.04 as controller node and CentOS 6.6 as compute node (Icehouse). When I try to create an instance, it directly goes into the ERROR state without even scheduling. The scheduler log shows the following results.

2015-04-27 18:12:22.981 18418 INFO nova.scheduler.filter_scheduler [req-d47d9182-e954-4deb-9594-44127943f2b4 14d3a406499e4c6c9eb8689213028fa8 f42a337f93e5493bb538c6954aa0eb82] Attempting to build 1 instance(s) uuids: [u'f1b0f0f8-1ae8-409c-9c8a-48f0d32f2242']
2015-04-27 18:12:23.042 18418 INFO nova.filters [req-d47d9182-e954-4deb-9594-44127943f2b4 14d3a406499e4c6c9eb8689213028fa8 f42a337f93e5493bb538c6954aa0eb82] Filter RamFilter returned 0 hosts
2015-04-27 18:12:23.044 18418 WARNING nova.scheduler.driver [req-d47d9182-e954-4deb-9594-44127943f2b4 14d3a406499e4c6c9eb8689213028fa8 f42a337f93e5493bb538c6954aa0eb82] [instance: f1b0f0f8-1ae8-409c-9c8a-48f0d32f2242] Setting instance to ERROR state.
2015-04-27 18:12:23.629 18418 INFO oslo.messaging._drivers.impl_rabbit [-] Connected to AMQP server on
edit retag flag offensive close merge delete

2 answers

Sort by ยป oldest newest most voted

answered 2015-04-29 02:06:16 -0500

Zishan gravatar image

OK, now I am able to launch the first instance using Ubuntu qcow2 image but I get an ERROR when I try to launch another one. If I use CirrOS, I can launch upto 3 or 4 instances after which I get ERROR while launching instances. My dashboard limit summary shows a lot of free space. What could the problem be?

edit flag offensive delete link more

answered 2015-04-27 12:23:55 -0500

dbaxps gravatar image
edit flag offensive delete link more


I have deleted all the instances but I am still unable to launch any. However, my disk size is less. Is that a problem?

[root@compute ~]# df -Th

Filesystem Type Size Used Avail Use% Mounted on /dev/mapper/vg_compute-lv_root

                 ext4   6.5G  4.0G  2.3G  64% /

tmpfs tmpfs 499M 72K 499M 1% /dev/shm /dev/sda1 ext4 477M 29M 424M 7% /boot

Zishan gravatar imageZishan ( 2015-04-28 00:52:04 -0500 )edit

Try cirros as m1.tiny. m1.small won't work for sure.

dbaxps gravatar imagedbaxps ( 2015-04-28 01:00:11 -0500 )edit

Tried that as well, didn't work either. Instance instantly goes into ERROR state.

Zishan gravatar imageZishan ( 2015-04-28 01:39:31 -0500 )edit

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


Asked: 2015-04-27 07:57:27 -0500

Seen: 1,005 times

Last updated: Apr 29 '15