Looking at the job in pike, nova-compute would run with nova.conf rather than nova-cpu.conf:
http://logs.openstack.org/11/627011/2/check/legacy-grenade-dsvm-neutron-multinode-live-migration/6e4c69c/logs/new/screen-n-cpu.txt.gz#_2019-01-07_14_12_37_218
2019-01-07 14:12:37.218 19245 DEBUG oslo_service.service [req-8874018b-41f7-4799-b7cf-a57d8a5f0367 - -] command line args: ['--config-file', '/etc/nova/nova.conf'] log_opt_values /usr/local/lib/python2.7/dist-packages/oslo_config/cfg.py:2863
There actually isn't a nova-cpu.conf in that job:
http://logs.openstack.org/11/627011/2/check/legacy-grenade-dsvm-neutron-multinode-live-migration/6e4c69c/logs/etc/nova/
Looking at the job in pike, nova-compute would run with nova.conf rather than nova-cpu.conf:
http:// logs.openstack. org/11/ 627011/ 2/check/ legacy- grenade- dsvm-neutron- multinode- live-migration/ 6e4c69c/ logs/new/ screen- n-cpu.txt. gz#_2019- 01-07_14_ 12_37_218
2019-01-07 14:12:37.218 19245 DEBUG oslo_service. service [req-8874018b- 41f7-4799- b7cf-a57d8a5f03 67 - -] command line args: ['--config-file', '/etc/nova/ nova.conf' ] log_opt_values /usr/local/ lib/python2. 7/dist- packages/ oslo_config/ cfg.py: 2863
There actually isn't a nova-cpu.conf in that job:
http:// logs.openstack. org/11/ 627011/ 2/check/ legacy- grenade- dsvm-neutron- multinode- live-migration/ 6e4c69c/ logs/etc/ nova/