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

Bug #1566942 reported by Sean M. Collins on 2016-04-06
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack Compute (nova)

Bug Description

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:

Matt Riedemann (mriedem) wrote :

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

tags: added: live-migration
Sean M. Collins (scollins) wrote :

updated description with the exact SHA.

description: updated
description: updated
Matt Riedemann (mriedem) wrote :

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

Matt Riedemann (mriedem) wrote :

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

Changed in nova:
status: New → Invalid
Sean M. Collins (scollins) wrote :

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.

Matt Riedemann (mriedem) on 2016-04-06
tags: added: config

Change abandoned by Michael Still (<email address hidden>) on branch: master
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.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers