Instance waiting on scheduling

Asked by Harshavardhana

Hi Everyone,

I have been following this blog in test environment with just one node running.

I have completed till the process of

euca-run-instances $emi -k mykey -t m1.tiny

But all i am seeing now is the instance is just waiting for scheduling for an Hr or so

RESERVATION r-lcb18uqx myproject default
INSTANCE i-00000002 ami-xggshuo1 scheduling mykey (myproject, None) 0 m1.tiny2011-02-18 22:26:19.277799 unknown zone

http://fnords.wordpress.com/2010/12/02/bleeding-edge-openstack-nova-on-maverick/

Is there anything that i missed here? can any one help me.

Regards

Question information

Language:
English Edit question
Status:
Solved
For:
OpenStack Compute (nova) Edit question
Assignee:
No assignee Edit question
Solved by:
Harshavardhana
Solved:
Last query:
Last reply:
Revision history for this message
Anne Gentle (annegentle) said :
#1

There is some troubleshooting information on this page that may help you. http://docs.openstack.org/openstack-compute/admin/content/ch08s03.html

Revision history for this message
Harshavardhana (harsha-gluster) said :
#2

I have seen that but the current problem i have is the instance is stuck at scheduling, there are no such enough warning or error messages.

The error which is described in documentation is for pending instances, for now i can't even create one with libvirt.xml if i had to since i don't have it where its supposed.

Looks like i am missing something from the blog.

root@ubuntu1010template:/var/log/libvirt/qemu# ls -ltr
total 0
root@ubuntu1010template:/var/log/libvirt/qemu#

Revision history for this message
Anne Gentle (annegentle) said :
#3

When I've had this happen to me, it was a network problem or a bug in trunk.

Trunk is changing extremely rapidly right now. Perhaps if you reinstall using ppa:nova-core/release your image will launch.

From Wayne, who is a great troubleshooter: "Since you have already installed the /trunk PPA, you'll have to make sure to disable it, and uninstall the nova-* packages. Then add the /release PPA, and apt-get all the nova-* packages again. Not sure on the python dependencies that are brought down, so if it's not too much hassle a reinstall might be worth it."

Good luck - let us know how it goes.

Revision history for this message
Harshavardhana (harsha-gluster) said :
#4

Well after re installation of everything

root@ubuntu1010template:~# euca-describe-instances
RESERVATION r-pp418fvo myproject default
INSTANCE i-0000000c ami-xggshuo1 10.1.80.6 10.1.80.6 pending mykey (myproject, ubuntu1010template) 0m1.tiny 2011-02-21 19:24:01.777161 nova
root@ubuntu1010template:~#

Stays pending for ever.

Revision history for this message
Christian Berendt (berendt) said :
#5

What says the logfile of nova-compute?

Revision history for this message
Harshavardhana (harsha-gluster) said :
#6

I think i saw the problem in libvirt.xml which was pointing for kvm as "type" this resulted in hangs since i was testing inside a virtual machine, looks like the libvirt was defaulting things to 'kvm' . Changing that to qemu everything started working.

Revision history for this message
Harshavardhana (harsha-gluster) said :
#7

I think i saw the problem in libvirt.xml which was pointing for kvm as "type" this resulted in hangs since i was testing inside a virtual machine, looks like the libvirt was defaulting things to 'kvm' . Changing that to qemu everything started working.