euca-create-volume stuck in 'creating'

Asked by Jon Slenk on 2011-07-21

Cactus nova. Trying to get nova-volume going. Got to the point where euca-describe-volumes shows my new volume as 'creating'. But it seems like it will never get done. Couldn't find any docs on how long one might expect such things to take. Don't see anything useful status wise about the progression of the creation in any logs.

It would be great if there were a way to get insight into what is or is not happening. To know if I have to just be really durned patient, or if something is fundamentally misconfigured and preventing completion. Thanks.

Question information

Language:
English Edit question
Status:
Solved
For:
OpenStack Compute (nova) Edit question
Assignee:
No assignee Edit question
Solved by:
Jon Slenk
Solved:
2011-07-22
Last query:
2011-07-22
Last reply:
2011-07-21
Vish Ishaya (vishvananda) said : #1

Create volume should be pretty fast.

Does the volume show which host it was sent to? If it gets to creating and hangs you should get a traceback in either the nova-volume (if it has a host set) log or perhaps in the api or scheduler log (if it doesn't).

On Jul 21, 2011, at 2:46 PM, Jon Slenk wrote:

> New question #165606 on OpenStack Compute (nova):
> https://answers.launchpad.net/nova/+question/165606
>
> Cactus nova. Trying to get nova-volume going. Got to the point where euca-describe-volumes shows my new volume as 'creating'. But it seems like it will never get done. Couldn't find any docs on how long one might expect such things to take. Don't see anything useful status wise about the progression of the creation in any logs.
>
> It would be great if there were a way to get insight into what is or is not happening. To know if I have to just be really durned patient, or if something is fundamentally misconfigured and preventing completion. Thanks.
>
> --
> You received this question notification because you are a member of Nova
> Core, which is an answer contact for OpenStack Compute (nova).

Jon Slenk (jslenk) said : #2

Many thanks for your note.

> Does the volume show which host it was sent to?

(If the man page for euca-describe-volumes said what the columns even were, I might be better able to answer :-)

Here's the line from euca-describe-volumes:
VOLUME vol-00000001 1 nova creating (default-project, None, None, None) 2011-07-21T21:03:00Z

Notes:
a) I'm trying to do this locally all on a single machine so far (dd, loop0, nova-volumes). So it shouldn't have been dispatched to any other machine, I think.
b) I've trawled the /var/log/nova/* logs but don't find anything obviously relevant.
c) When I try "nova-manage volume delete vol-00000001" the command fails; the log shows VolumeNotFound: Volume 1 not found raised.
d) I tried the trick mentioned in another ticket of having to manually create a small initial logical volume in the nova-volumes group, but that hasn't improved anything. Tried doing another create after that, and it is likewise stuck and undeleteable.

At some point I will try to redo things from scratch yet again in the hopes of there having been some configuration issue I've missed or gotten wrong along the way.

Jon Slenk (jslenk) said : #3

an update: New stuff has come to light (a la Big Lebowski) about our local setup that I didn't realize, so I'm working through that to see if it helps any. [Even if that fixes things, it would be nice if some day in some distant idyllic future, the code involved in setting up volumes somehow offered more transparency about what is/not happening vs. apparently silent failure. :-]

Jon Slenk (jslenk) said : #4

Now working. I think the fundamental deal is that the machines I was originally trying it on had some of nova & eucalyptus installed, but were not in fact really fully properly connected with the overall nova system. When I moved over to a machine that was actually part of the nova setup then things worked lickety-split.

(The sad/odd thing is that the failed attempts didn't give much of any indication of why they failed, and they have managed to populate whatever database lists the nova volumes because I still see them listed when I do euca-describe-volumes on the working machine. So the non-happy-path code for nova-volumes is unfortunately a wee bit too silent imhumbleo.)

Vish Ishaya (vishvananda) said : #5

So one of the None in the parens should be a host name. Therefore your request never got sent to nova-volume. You should have an error in scheduler log about NoValidHost, or perhaps api log if there is some other error. You should also check nova-manage service list and make sure you have smilies.

Vish

On Jul 21, 2011, at 3:56 PM, Jon Slenk wrote:

> Question #165606 on OpenStack Compute (nova) changed:
> https://answers.launchpad.net/nova/+question/165606
>
> Jon Slenk posted a new comment:
> an update: New stuff has come to light (a la Big Lebowski) about our
> local setup that I didn't realize, so I'm working through that to see if
> it helps any. [Even if that fixes things, it would be nice if some day
> in some distant idyllic future, the code involved in setting up volumes
> somehow offered more transparency about what is/not happening vs.
> apparently silent failure. :-]
>
> --
> You received this question notification because you are a member of Nova
> Core, which is an answer contact for OpenStack Compute (nova).