yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #77262
[Bug 1818092] Re: hypervisor check in _check_instance_has_no_numa() is broken
Reviewed: https://review.openstack.org/635350
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=4da058723332a58323640fabce3d95902946a07d
Submitter: Zuul
Branch: master
commit 4da058723332a58323640fabce3d95902946a07d
Author: Chris Friesen <chris.friesen@xxxxxxxxxxxxx>
Date: Wed Feb 6 14:57:12 2019 -0600
fix up numa-topology live migration hypervisor check
It turns out that even when KVM is supported by qemu the libvirt
driver will report the hypervisor type as "QEMU". So we need to
fix up the hypervisor type check in the live migration code that
checks whether the instance has a NUMA topology.
Closes-Bug: #1818092
Change-Id: I5127227a1e3d76dd413a820b048547ba578aff6b
Signed-off-by: Chris Friesen <chris.friesen@xxxxxxxxxxxxx>
** Changed in: nova
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1818092
Title:
hypervisor check in _check_instance_has_no_numa() is broken
Status in OpenStack Compute (nova):
Fix Released
Bug description:
In commit ae2e5650d "Fail to live migration if instance has a NUMA
topology" there is a check against hypervisor_type.
Unfortunately it tests against the value "obj_fields.HVType.KVM".
Even when KVM is supported by qemu the libvirt driver will still
report the hypervisor type as "QEMU". So we need to fix up the
hypervisor type check otherwise we'll always fail the check.
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1818092/+subscriptions
References