Comment 8 for bug 1695634

The problem is the compute node isn't getting registered with the placement service before the server create request is made. The scheduler asks placement for the list of resource providers (compute nodes) to service a given build request, and it's getting 0 back.

We can see that before the compute host is registered with the cell, it's failing to register the compute node with placement here:

http://logs.openstack.org/95/468095/2/gate/gate-shade-functional/3f5d8dc/logs/screen-n-cpu.txt.gz#_Jun_02_12_46_14_556997

It's getting a 503 response back.

5 seconds later we map the compute host to the cell:

2017-06-02 12:46:19.540 | Creating host mapping for compute host 'ubuntu-xenial-osic-cloud1-s3500-9104911': bc5499e9-2e12-4ae6-9e5b-58b8104de163

40 seconds later the scheduler is asked to find a host for the server create request, which asks placement for hosts and gets 0 back:

Jun 02 12:46:59.055921 ubuntu-xenial-osic-cloud1-s3500-9104911 nova-scheduler[20766]: DEBUG nova.filters [None req-a92036cd-3f52-41d6-b104-cb446cfa0ca1 demo demo] Starting with 0 host(s) {{(pid=20766) get_filtered_objects /opt/stack/new/nova/nova/filters.py:70}}

And finally 15 seconds after that, the compute node is registered with placement successfully:

http://logs.openstack.org/95/468095/2/gate/gate-shade-functional/3f5d8dc/logs/screen-n-cpu.txt.gz#_Jun_02_12_47_14_576829

Jun 02 12:47:14.576829 ubuntu-xenial-osic-cloud1-s3500-9104911 nova-compute[21934]: INFO nova.scheduler.client.report [None req-7d543fdf-c132-45b4-b7a3-7a9c697419d0 None None] [req-f0bc362e-3492-4338-933b-5adf88a01b49] Created resource provider record via placement API for resource provider with UUID bc5499e9-2e12-4ae6-9e5b-58b8104de163 and name ubuntu-xenial-osic-cloud1-s3500-9104911.