Ask Your Question
2

How to troubleshoot an instance stuck on 'BUILD'?

asked 2014-03-25 09:16:16 -0500

Daniel P gravatar image

Greetings! I'm running through the 'Openstack Installation Guide for Ubuntu 12.04 (LTS)'. I've attempted to launch an instance on the setup and it seems to be stuck on status 'BUILD'.

On the compute node in /var/log/nova/nova-compute.log I find:

2014-03-25 14:28:32.614 2096 AUDIT nova.compute.manager [req-58413990-f719-4645-9ddc-7040aa15e276 a4ce64aa1c994b709cdcfc4c6512d4ee 73cea9b8c27845f185c90168f3ab786a] [instance: 01b2b53f-e0ee-4980-9b72-fc5c351190a7] Starting instance...

I've looked through all the other logs on the compute node, and several of the logs on the controller as well, but I don't see any errors; it seems to be largely silent.

Any suggestions on how I can troubleshoot this and narrow down possible causes?

It may be useful to mention that I'm installing on an Ubuntu Trusty server daily build, with the openstack packages from the trusty repo, so what will soon be Icehouse I suppose.

edit retag flag offensive close merge delete

Comments

I guess you need to enable debug logs in nova-compute (and restart service) to get an any clues regarding where compute is getting blocked!

unmesh-gurjar gravatar imageunmesh-gurjar ( 2014-03-25 10:24:41 -0500 )edit
add a comment

2 answers

Sort by ยป oldest newest most voted
1

answered 2014-08-20 04:34:21 -0500

DeLpYne gravatar image

I had faced the same issue. Resolved it by simply restarting the compute service.

On the compute node execute service nova-compute restart

After that, terminate the instance which is in build state. Then, on the controller execute the nova boot command again to spawn the instance.

edit flag offensive delete link more
add a comment
0

answered 2014-04-01 09:02:34 -0500

Daniel P gravatar image

I did solve the problem. I've been installing on a daily build of Trusty and using the openstack packages directly from the Trusty repo. I'd been using the Havana install guide, and that was my mistake. When I followed the configuration instructions in the dev guide (which will become documentation for Icehouse) there were some differences, and it solved this problem. I don't remember the exact differences that got it working, but the short of the story is that the Havana instructions don't work with the pre-release Icehouse packages.

@unmesh-gurjar - thank you for your comment. Turning on debug generally a good starting strategy to narrow down problems, which I'm about to employ for another problem I've hit with VNC!

edit flag offensive delete link more
add a comment

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

subscribe to rss feed

Stats

Asked: 2014-03-25 09:16:16 -0500

Seen: 6,757 times

Last updated: Apr 01 '14

Related questions

Opensatck Trove Instance Stuck at Build State

nova instances stuck on icehouse

Unable to start any new VMs - stuck in build / scheduling status [closed]

Instance stuck in build status

how to open a port of an instance?

http://127.0.0.1:6010/recon/replication: <urlopen error [Errno 111] ECONNREFUSED>

Replicate a VM in openstack

instance spawn error

instances wont start mitaka to newton

Can I reboot an instance with a new flavor?