Comment 1 for bug 1813216

One thing I noticed is that the script that sets up the grenade + live migration environment is trying to use nova.conf rather than nova-cpu.conf here:

https://github.com/openstack/nova/blob/5283b464b5c4976224a8d7ea3898dfe3e6bec786/nova/tests/live_migration/hooks/run_tests.sh#L57

But that's not happening and I'm seeing nova-compute running with nova-cpu.conf:

http://logs.openstack.org/04/632904/2/check/legacy-grenade-dsvm-neutron-multinode-live-migration/8f886af/logs/screen-n-cpu.txt.gz#_Jan_24_19_59_15_757250

Jan 24 19:59:15.757250 ubuntu-xenial-ovh-bhs1-0002106526 nova-compute[31553]: DEBUG oslo_service.service [None req-b65724f9-3239-41b5-88be-f7f3c932e931 None None] command line args: ['--config-file', '/etc/nova/nova-cpu.conf'] {{(pid=31553) log_opt_values /usr/local/lib/python2.7/dist-packages/oslo_config/cfg.py:3008}}

And I'm not seeing that $GRENADE_OLD_BRANCH check get run in the console logs, so probably need to add some debug logging to see where that variable comes from, but I do see it here:

http://logs.openstack.org/04/632904/2/check/legacy-grenade-dsvm-neutron-multinode-live-migration/8f886af/logs/devstack-gate-setup-host.txt.gz

  GRENADE_NEW_BRANCH: master
  GRENADE_OLD_BRANCH: stable/rocky