in Neuton release and i have followed all the steps of openstack guide and did duble cross check of the configuration, but whenever i am trying to launch any instance it stuck on Scheduling process i tried all the steps

asked 2017-03-30 07:49:30 -0500

nitin gautam gravatar image

at my compute node i found below logs at /var/log/nova/nova-compute.log

2017-03-30 08:44:17.511 7475 INFO nova.compute.resource_tracker [req-39b32f33-bf4c-46d1-89c8-f36c75509ccf - - - - -] Auditing locally available compute resources for node compute1
2017-03-30 08:44:17.687 7475 INFO nova.compute.resource_tracker [req-39b32f33-bf4c-46d1-89c8-f36c75509ccf - - - - -] Total usable vcpus: 4, total allocated vcpus: 0
2017-03-30 08:44:17.688 7475 INFO nova.compute.resource_tracker [req-39b32f33-bf4c-46d1-89c8-f36c75509ccf - - - - -] Final resource view: name=compute1 phys_ram=16244MB used_ram=512MB phys_disk=186GB used_disk=0GB total_vcpus=4 used_vcpus=0 pci_stats=[]
2017-03-30 08:44:17.752 7475 INFO nova.compute.resource_tracker [req-39b32f33-bf4c-46d1-89c8-f36c75509ccf - - - - -] Compute_service record updated for compute1:compute1

nothing unusual at any other logs

edit retag flag offensive close merge delete



Scheduling means that the controller is still trying to find a host for your instance. Check the scheduler and the conductor logs on the controller(s). You can also switch on debugging by setting the DEBUG flag in nova.conf and restarting the scheduler and conductor.

Bernd Bausch gravatar imageBernd Bausch ( 2017-03-30 11:43:21 -0500 )edit

so far i got those logs from my nova-api

nitin gautam gravatar imagenitin gautam ( 2017-03-31 07:43:27 -0500 )edit

I can't read the log; it's on a single line. Besides, the scheduler and conductor logs will help; the api log probably won't.

Bernd Bausch gravatar imageBernd Bausch ( 2017-04-01 02:50:10 -0500 )edit

Ok please find below log links as you asked.

Conductor's log

scheduler log

compute log's

nitin gautam gravatar imagenitin gautam ( 2017-04-03 00:24:13 -0500 )edit

These logs don't indicate that an instance is being launched, or that anything unexpected or erroneous happens. Perhaps the API log is useful after all. Ensure that you provide the log entries around the time the instance was launched.

Bernd Bausch gravatar imageBernd Bausch ( 2017-04-03 00:53:58 -0500 )edit