OpenStack Dashboard (Horizon)

instances stuck in status = build and task = deleting

Asked by Glen

Hi Community,

We just started implementing Openstack within our organization over the last week. We are implementing the current release Essex. Here is the version: 2012.1 (2012.1-LOCALBRANCH:LOCALREVISION). We have installed the controller on a fedora 17 machine and the nodes are centos 6.

The problem we are seeing is that our instances get "stuck" in a build state. They are visible in the dashboard but they do not progress past the "Scheduling" (under task), it just stays that way. If i try to delete the instance the task changes from Scheduling to Deleting. However, the instance never goes away. I can't seem to track down what the issue is. I found this bug https://bugs.launchpad.net/nova/+bug/907808 but according to the status it was fixed and committed to the essex-3 2012.1 milestone which is the one I am trying to use. Is there an update I'm missing?

In troubleshooting this issue ive examined all the logs, verified the services are running, that the controller sees the node and vice-versa, but am still stuck. What next???

Let me know if you need any information that I have ommitted. Also, if I need to post this someplace else please let me know. I am new to the community.

Thanks in advance for your help on this.

Glen

Question information

Language:
English Edit question
Status:
Solved
For:
OpenStack Dashboard (Horizon) Edit question
Assignee:
No assignee Edit question
Solved by:
Glen
Solved:
Last query:
Last reply:
Revision history for this message
Glen (glen-boland) said : 		#1

update

I found that I could get the dashboard to clear out the images by setting the deleted flag in the database. Which took care of the first issue. However, I still wasn't able to get the instance to launch successfully so started over and was able to get it to work.

Revision history for this message
Gabriel Hurley (gabriel-hurley) said : 		#2

The dashboard is simply displaying the current state of the instances as Nova reports it; this is not a Horizon issue at all. Marking an item as "deleted" in the database pushes it out of the DB filter for things Nova reports back via the API, however it doesn't do the associated cleanup that should happen before it being marked as deleted.

That said, there are many ways to wedge Nova in a state that it will never clear out the instances. I would recommend asking on the OpenStack mailing list or on the Nova project.