[openstack-dev] 回复: [nova][nova-scheduler] Instance boot stuck in"Scheduling" state

Matt Riedemann mriedemos at gmail.com
Tue Mar 14 15:31:40 UTC 2017

On 3/14/2017 10:22 AM, Prashant Shetty wrote:
> Couple of things to check,
>   * On controller in nova.conf you should have [placement] section with
>     below info
>       o [placement]
>         os_region_name = RegionOne
>         project_domain_name = Default
>         project_name = service
>         user_domain_name = Default
>         password = <password>
>         username = placement
>         auth_url = <auth_url>
>         auth_type = password
>   * If nova service-list shows your nova-compute is UP and RUNNING, you
>     need to run discover commands on controller as below
>       o nova-manage cell_v2 map_cell0 --database_connection <db_url>
>       o nova-manage cell_v2 simple_cell_setup --transport-url
>         <transport_url>
>       o nova-manage cell_v2 discover_hosts --verbose
> Discover command should show message that it has discovered your compute
> nodes. In case still instance launch fails check nova-conductor and
> nova-scheduler logs for more info.
> For more information refer,
> https://docs.openstack.org/developer/nova/cells.html
> Thanks,
> Prashant

Those are all good things to check. If placement is not properly 
configured and running though, the nova-compute service won't start and 
the scheduling attempt will result in a NoValidHost error which should 
put the instance into ERROR state.

Starting in Ocata, if you're not using cellsv1, the instance should be 
created in the nova_cell0 database. But it should be there with ERROR 
state and you should still be able to list/show it from the API so you 
can delete it. It shouldn't be left in scheduling state.

You may want to run this to make sure your setup is done properly:

nova-status upgrade check

That should give you some basic readiness/health information about cells 
v2 and placement in your setup.




More information about the OpenStack-dev mailing list