Traceback while scheduling both overcloud nodes on tripleo ci
Last succesfull run was 05-Sep-2013 01:54:10 (UTC)
So something changed after this run https://review.openstack.org/#/c/43968/
although scheduling of baremetal node seems to work on seed ....
INFO nova.scheduler.filter_scheduler [req-c754d309-92fc-461a-81fb-d5bfe97a0676 99fa1214e35a4cc6b99c9332b8ca66fb d86556c4d57c4dfc87b30f6c66c40a98] Attempting to build 1 instance(s) uuids: [u'f71e3e47-f2a2-4a13-9
WARNING nova.scheduler.utils [req-c754d309-92fc-461a-81fb-d5bfe97a0676 99fa1214e35a4cc6b99c9332b8ca66fb d86556c4d57c4dfc87b30f6c66c40a98] Failed to scheduler_run_instance: 'service'
WARNING nova.scheduler.utils [req-c754d309-92fc-461a-81fb-d5bfe97a0676 99fa1214e35a4cc6b99c9332b8ca66fb d86556c4d57c4dfc87b30f6c66c40a98] [instance: f71e3e47-f2a2-4a13-92c0-c3397acaf409] Setting instance to ERR
ERROR nova.openstack.common.rpc.amqp [req-c754d309-92fc-461a-81fb-d5bfe97a0676 99fa1214e35a4cc6b99c9332b8ca66fb d86556c4d57c4dfc87b30f6c66c40a98] Exception during message handling
TRACE nova.openstack.common.rpc.amqp Traceback (most recent call last):
TRACE nova.openstack.common.rpc.amqp File "/opt/stack/venvs/nova/lib/python2.7/site-packages/nova/openstack/common/rpc/amqp.py", line 461, in _process_data
TRACE nova.openstack.common.rpc.amqp **args)
TRACE nova.openstack.common.rpc.amqp File "/opt/stack/venvs/nova/lib/python2.7/site-packages/nova/openstack/common/rpc/dispatcher.py", line 172, in dispatch
TRACE nova.openstack.common.rpc.amqp result = getattr(proxyobj, method)(ctxt, **kwargs)
TRACE nova.openstack.common.rpc.amqp File "/opt/stack/venvs/nova/lib/python2.7/site-packages/nova/scheduler/manager.py", line 160, in run_instance
TRACE nova.openstack.common.rpc.amqp context, ex, request_spec)
TRACE nova.openstack.common.rpc.amqp File "/opt/stack/venvs/nova/lib/python2.7/site-packages/nova/scheduler/manager.py", line 147, in run_instance
TRACE nova.openstack.common.rpc.amqp legacy_bdm_in_spec)
TRACE nova.openstack.common.rpc.amqp File "/opt/stack/venvs/nova/lib/python2.7/site-packages/nova/scheduler/filter_scheduler.py", line 87, in schedule_run_instance
TRACE nova.openstack.common.rpc.amqp filter_properties, instance_uuids)
TRACE nova.openstack.common.rpc.amqp File "/opt/stack/venvs/nova/lib/python2.7/site-packages/nova/scheduler/filter_scheduler.py", line 326, in _schedule
TRACE nova.openstack.common.rpc.amqp hosts = self.host_manager.get_all_host_states(elevated)
TRACE nova.openstack.common.rpc.amqp File "/opt/stack/venvs/nova/lib/python2.7/site-packages/nova/scheduler/host_manager.py", line 432, in get_all_host_states
TRACE nova.openstack.common.rpc.amqp service = compute['service']
TRACE nova.openstack.common.rpc.amqp KeyError: 'service'
TRACE nova.openstack.common.rpc.amqp
This particular error is caused by this change https:/ /review. openstack. org/#/c/ 43151/ , but the real problem is deeper: /review. openstack. org/#/c/ 43151/ was merged and changed the way the tables were joined.
ComputeNode <--> Service must be a 1-1 relationship, but there is no unique constraint on service_id column of compute_nodes table. Because of this, duplicate entries (referring to the same service row) can be added to compute_nodes table. This error had passed silently before https:/