Add a workaround to skip hypervisor version check on live migration
Bug #1982853 reported by
Kashyap Chamarthy
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Fix Released
|
Low
|
Kashyap Chamarthy |
Bug Description
What?
-----
Add a workaround config option (that will be disabled by default) that will disable the version-checking of hypervisors during live-migration.
Why?
----
It can be useful for operators in certain scenarios when upgrading. E.g. if you want to relocate all instances off a compute node due to an emergency hardware issue, and you only have another old compute node ready at the time.
Note, though: libvirt will do its own internal compatibility checks, and might still reject live migration if the destination is incompatible.
Changed in nova: | |
importance: | Wishlist → Low |
Changed in nova: | |
status: | Triaged → In Progress |
To post a comment you must log in.
This is really just a nice to have option for operators that find them selves in an unfortunate situation where they need to move vms to an old hypervisor e.g. rolling back an upgrade or unexpected hardware failure in the middle of an rolling upgrade.
it is not a bug in nova itself nor is it really a feature since it not something we would ever enable by default.
so triaging this as wishlist since its nice to have but not strictly required.
you can use cold migration in this case and if the VM is using a feature form the new hypervisor release that will still be required.
as noted libvirt will do its own internal check and if the VM is using a feature not supported by the dest host it will still reject the live migration. so this is safe but suboptimal since this would make the failure much later in this case.
for operator that are manually intervening and know that the VM will work on the dest the scheduling pessimisation is not a concern and since livemigation is an admin only operation i think this is oke as a workaround.