Ask Your Question
2

Launching instance. Spawning state

asked 2014-11-24 05:00:49 -0500

Pablo Revuelta gravatar image

updated 2014-11-24 05:27:10 -0500

Hello!! When I launch an instance from my dashboard, it will be in a spawning state forever. I have looked at the logs in /var/log/nova but I have not seen any error.

[root@vmlbcatfl49 ~(keystone_admin)]# for file in $(ls /var/log/nova/); do cat /var/log/nova/$file | grep error; done
[root@vmlbcatfl49 ~(keystone_admin)]

The only weird thing I have found is that, the last line of my scheduler.log logfile:

2014-11-24 11:32:02.142 3675 INFO nova.scheduler.filter_scheduler [req-6bd0507e-69da-4d3a-99d1-4090fb94a626 a10b12add69e4199aee36cb743d73b6c a5cb7bf38ac941acbed0f569c1d1d3e6] Choosing host WeighedHost [host: vmlbcatfl49.lvtc.gsnet.corp, weight: 1.0] for instance 726289a0-1dae-479c-8868-d892085ca174

Could you help me please?

FROM 9lives answer:

[root@vmlbcatfl49 ~(keystone_admin)]# for file in $(ls /var/log/nova/); do cat /var/log/nova/$file | grep -iE 'error|warn' ; done
2014-11-24 10:53:46.675 10308 WARNING keystoneclient.middleware.auth_token [-] Configuring admin URI using auth fragments. This is deprecated, use 'identity_uri' instead.
2014-11-24 10:53:46.682 10308 WARNING keystoneclient.middleware.auth_token [-] Configuring admin URI using auth fragments. This is deprecated, use 'identity_uri' instead.
2014-11-24 10:53:46.891 10308 WARNING keystoneclient.middleware.auth_token [-] Configuring admin URI using auth fragments. This is deprecated, use 'identity_uri' instead.
2014-11-24 11:20:40.891 3543 WARNING keystoneclient.middleware.auth_token [-] Configuring admin URI using auth fragments. This is deprecated, use 'identity_uri' instead.
2014-11-24 11:20:40.896 3543 WARNING keystoneclient.middleware.auth_token [-] Configuring admin URI using auth fragments. This is deprecated, use 'identity_uri' instead.
2014-11-24 11:20:41.094 3543 WARNING keystoneclient.middleware.auth_token [-] Configuring admin URI using auth fragments. This is deprecated, use 'identity_uri' instead.
2014-11-24 10:57:56.438 13621 WARNING nova.conductor.api [req-6c87d365-1407-4a09-ace4-41e4348debed None None] Timed out waiting for nova-conductor. Is it running? Or did this service start before nova-conductor?
2014-11-24 10:57:56.887 13621 WARNING nova.virt.libvirt.driver [req-b8efb854-9e5b-4ec2-a13b-de1106683675 None None] Cannot update service status on host: vmlbcatfl49.lvtc.gsnet.corp,since it is not registered.
2014-11-24 11:07:46.567 13621 WARNING nova.compute.manager [-] Bandwidth usage not supported by hypervisor.
2014-11-24 11:20:50.164 3573 WARNING nova.conductor.api [req-4800e4f8-4bc6-4c6a-a388-709882687d1c None None] Timed out waiting for nova-conductor. Is it running? Or did this service start before nova-conductor?
2014-11-24 11:30:39.930 3573 WARNING nova.compute.manager [-] Bandwidth usage not supported by hypervisor.
2014-11-24 11:40:41.450 3573 ERROR oslo.messaging.rpc.dispatcher [-] Exception during message handling: Instance instance-00000001 could not be found.
2014-11-24 11:40:41.480 3573 ERROR oslo.messaging._drivers.common [-] Returning exception Instance instance-00000001 could not be found. to caller
2014-11-24 11:40:41.480 3573 ERROR oslo.messaging._drivers.common [-] ['Traceback (most recent call last):\n', '  File "/usr/lib/python2.6/site-packages/oslo/messaging/rpc/dispatcher.py", line 133, in _dispatch_and_reply\n    incoming.message))\n', '  File "/usr/lib/python2.6/site-packages/oslo/messaging/rpc/dispatcher.py", line 176, in _dispatch\n    return self._do_dispatch(endpoint, method, ctxt, args)\n', '  File "/usr/lib/python2.6/site-packages/oslo/messaging/rpc/dispatcher.py", line 122, in _do_dispatch\n    result = getattr(endpoint, method ...
(more)
edit retag flag offensive close merge delete

Comments

Pablo, look at the instance log from the dashboard. If you are using a proper OS like Fedora or Ubuntu's image to spawn instances on a QEMU compute-host, it will take like 20 minutes for it to finish booting up. please post the instance logs and nova-compute logs.

Kashyap Kopparam gravatar imageKashyap Kopparam ( 2014-11-24 05:08:33 -0500 )edit

could you try this command, i really doubt there is error in nova-compute.log

for file in $(ls /var/log/nova/); do cat /var/log/nova/$file | grep -iE 'error|warn' ; done`
9lives gravatar image9lives ( 2014-11-24 05:21:36 -0500 )edit

First of all, thx a lot for answering me:

9lives, you were right. I will edit my question with the logs that kashyapk requestd and the output of your command because they are too long.

Pablo Revuelta gravatar imagePablo Revuelta ( 2014-11-24 05:25:06 -0500 )edit

kashyapk: They are very large logs, what do you want me to look for on them? :) thx a lot mate!! 9lives: I have already edited my answer with the output of your command. Thx !!

Pablo Revuelta gravatar imagePablo Revuelta ( 2014-11-24 05:28:49 -0500 )edit

9lives' command showed you the error you were looking for. You were missing the -i flag in grep command, else you would have seen the error before you even posted here :P. Ignore my requested logs.

Kashyap Kopparam gravatar imageKashyap Kopparam ( 2014-11-24 05:44:44 -0500 )edit

2 answers

Sort by ยป oldest newest most voted
0

answered 2014-11-25 02:07:42 -0500

Pablo Revuelta gravatar image

Hello vinoth. Thx for taking time to answer me :). I got allinone installation, so I only got one node. I have checked the services with nova service-list and everything is running :S

edit flag offensive delete link more
0

answered 2014-11-24 19:47:50 -0500

Vinoth gravatar image

Spawning state is the process of coping the image from glance repository to compute node. So that the hypervisor can use that image to create VMs.

Before copying the image from glance to the compute node, Nova scheduler start looking for suitable compute node with free resources. Once suitable compute node is available then nova scheduler schedule the process of spawning to that compute node.

If any thing went wrong while choosing the compute node, then the instance state will be put in spawning state forever.

So in your case, check for all the nova service running in both controller & compute node and restart it.

PS:- Spawning time depends on the size of an image usually it takes 2-5 minutes while launching the instance for the 1st time using that image on that compute node. Later instance launch process, spawning time usually takes in seconds.

While Using VMware ESXI as an hypervisor, Spawning takes long time(20-45 min) than usual for the 1st instance launch using that image.

edit flag offensive delete link more

Comments

any idea? Could it be due to libvirt version? Currently it is 0.10.

Pablo Revuelta gravatar imagePablo Revuelta ( 2014-11-25 06:58:32 -0500 )edit

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

Stats

Asked: 2014-11-24 05:00:49 -0500

Seen: 5,913 times

Last updated: Nov 24 '14