Ask Your Question

Instance forever spawning with RDO quickstart example "running an instance"

asked 2014-08-06 08:26:21 -0500

D43m0n gravatar image

Hi there,

I've followed RDO's (quickstart) example, specifically to get to know what Openstack has to offer. I'm running this on a supported server (HP DL380 G5) and RHEL6.5. The installation went as described. A few days later I wanted to continue with the rest of the quick start guide, for example the (running an instance) part. At Step 5: Launch the instance, I've launched the F19 image, and anxious to see what happens next, I'm waiting and waiting for the task "spawning" to complete. The instance F19-1 I've created is in that state for 40 minutes now. I've selected a sizing of m1.small with no additional settings on a server that has 8GB of RAM and a quad-core Xeon with a 72GB hard drive.

I've tried googling this issue "stuck at spawning" and found very little metoo's that are comparable to my set up. It's either a situation where things have worked before, or with a multi node setup, or after an upgrade. I'm following a quick start guide to the letter and have no clue of where to start looking.

For example, I've found (this) question and see the do_aug_close: you must call 'aug-init' first to initialize Augeas error too, but from what I understand, the symlink that's supposed to be missing, is already there.

The (other) issue I found tell's me nothing I can relate to since that seems to be a multi node setup with a lot of (debug) logging that's new to me and doesn't give me any lead.

I'd be happy to show logs, but which one? I can add everything but don't want to make this site less usable by dumping a load of logfiles which only mean something to the more experienced.

One thing I'd like to add, which might, or might not be related, or give an additional clue: While I was waiting for the instance to spawn, I continued with the next part of the quickstart: which is (setting up a floating ip-range). I determined I had to use neutron, instead of nova after reading (this) explanation. So I:

  1. sourced the keystone file,
  2. and started the command: neutron net-create public --router:external=True

and that command is also waiting for about 30 minutes now to complete. I've looked in the neutron logs, they're new to me and don't seem to contain any obvious errors. When looking at the load: load average: 0.68, 0.61, 0.60 and memory usage:

[root@ceres nova(keystone_admin)]# free
             total       used       free     shared    buffers     cached
Mem:       8057236    7783404     273832          0     142996    2547512
-/+ buffers/cache:    5092896    2964340
Swap:      2097144         52    2097092

and iostat I don ... (more)

edit retag flag offensive close merge delete

2 answers

Sort by ยป oldest newest most voted

answered 2014-08-09 05:57:34 -0500

D43m0n gravatar image

OK, I've asked myself do I need to edit my original question, or add an answer to it?

Well the direct answer to my question is yet to come, but I'd like to give a heads up on the status. Nothing changed. I decided to reinstall openstack using different methods of the packstack installer, but unfortunately other problems occur for which I'll ask another question.

edit flag offensive delete link more

answered 2014-08-10 14:05:51 -0500

Guillaume gravatar image


I already had this problem. Are you installing OpenStack on a virtual machine? If yes, you have to change the hypervisor type in /etc/nova/nova.conf. Search for virt_type and change it from 'kvm' to 'qemu'.

edit flag offensive delete link more


This installation of Openstack is on a physical server with VT enabled in the BIOS.

D43m0n gravatar imageD43m0n ( 2014-08-11 07:42:26 -0500 )edit

Get to know Ask OpenStack

Resources for moderators

Question Tools

1 follower


Asked: 2014-08-06 08:26:21 -0500

Seen: 702 times

Last updated: Aug 10 '14