I think it might be this change:
https://review.openstack.org/#/c/623284/
And looking at the grenade job failure, nova-compute is using nova.conf rather than nova-cpu.conf which is why it's hitting the API DB (which means something is wrong in devstack).
http://logs.openstack.org/80/630980/5/check/grenade-py3/49818d8/logs/screen-n-cpu.txt.gz#_Jan_17_08_04_32_547867
Jan 17 08:04:32.547867 ubuntu-xenial-inap-mtl01-0001764122 nova-compute[29129]: DEBUG oslo_service.service [None req-6462a6fa-ac8b-4802-bed8-18c335fc623f None None] command line args: ['--config-file', '/etc/nova/nova.conf'] {{(pid=29129) log_opt_values /usr/local/lib/python3.5/dist-packages/oslo_config/cfg.py:3008}}
I think it might be this change:
https:/ /review. openstack. org/#/c/ 623284/
And looking at the grenade job failure, nova-compute is using nova.conf rather than nova-cpu.conf which is why it's hitting the API DB (which means something is wrong in devstack).
http:// logs.openstack. org/80/ 630980/ 5/check/ grenade- py3/49818d8/ logs/screen- n-cpu.txt. gz#_Jan_ 17_08_04_ 32_547867
Jan 17 08:04:32.547867 ubuntu- xenial- inap-mtl01- 0001764122 nova-compute[ 29129]: DEBUG oslo_service. service [None req-6462a6fa- ac8b-4802- bed8-18c335fc62 3f None None] command line args: ['--config-file', '/etc/nova/ nova.conf' ] {{(pid=29129) log_opt_values /usr/local/ lib/python3. 5/dist- packages/ oslo_config/ cfg.py: 3008}}