Nova live-migrations cannot be done with mixed versions of nova-api and nova-compute

[Sean M. Collins]

When running a controller (nova was SHA b55d5bc), and nova-compute (from Liberty) on a separate node, and attempting to live-migrate instances off the liberty nova-compute, the following error occurs:

http://paste.openstack.org/show/492327/

[Matt Riedemann (mriedem)]

What is 'up to date' controller? Newton or Mitaka?

[Sean M. Collins (scollins)]

updated description with the exact SHA.

[Matt Riedemann (mriedem)]

What is the value of CONF.upgrade_levels.compute in your nova.conf?

[Matt Riedemann (mriedem)]

You need to set CONF.upgrade_levels.compute in your nova.conf on your controller node, see how the grenade multinode job sets this:

http://logs.openstack.org/18/295218/3/check/gate-grenade-dsvm-multinode/cb39c7b/logs/etc/nova/nova.conf.txt.gz

[Sean M. Collins (scollins)]

Not having a sane default for CONF.upgrade_levels.compute is a bug. Can we re-open this? I think it shows that there does need to be a better out-of-the-box configuration.

[OpenStack Infra (hudson-openstack)]

Related fix proposed to branch: master
Review: https://review.openstack.org/302341

[OpenStack Infra (hudson-openstack)]

Change abandoned by Michael Still (<email address hidden>) on branch: master
Review: https://review.openstack.org/302341
Reason: This patch has been sitting unchanged for more than 12 weeks. I am therefore going to abandon it to keep the nova review queue sane. Please feel free to restore the change if you're still working on it.