Comment 6 for bug 1709594

That's your nova.conf, but what about the nova-cpu.conf? That's not going to have the [api_database]/connection set, and that's probably your issue. The AggregateList.get_by_host code is looking up aggregates in the API database, and there is no connection set in the context for that, it's an up-call from the compute service, which is running isolated in the cell, to the API DB, and that's blocked in super-conductor mode.

e.g. http://logs.openstack.org/42/492242/1/check/gate-tempest-dsvm-neutron-multinode-full-ubuntu-xenial-nv/cfb2cad/logs/subnode-2/etc/nova/nova-cpu.conf.txt.gz

There is no database connection in there. The compute service is talking to the local cell conductor, which is using nova_cell1.conf:

http://logs.openstack.org/42/492242/1/check/gate-tempest-dsvm-neutron-multinode-full-ubuntu-xenial-nv/cfb2cad/logs/etc/nova/nova_cell1.conf.txt.gz

Which only has access to the cell database, not the API database.

The up-call limitations are described here:

https://docs.openstack.org/nova/latest/user/cellsv2_layout.html#operations-requiring-upcalls

So to workaround this in devstack, set CELLSV2_SETUP=singleconductor in your local.conf.