Reviewed: https://review.openstack.org/466143 Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=a2b0824aca5cb4a2ae579f625327c51ed0414d35 Submitter: Jenkins Branch: master
commit a2b0824aca5cb4a2ae579f625327c51ed0414d35 Author: Guang Yee <[email protected]> Date: Thu May 18 16:38:16 2017 -0700 make sure to rebuild claim on recreate On recreate where the instance is being evacuated to a different node, we should be rebuilding the claim so the migration context is available when rebuilding the instance. Change-Id: I53bdcf8edf640e97b4632ef7a093f14a6e3845e4 Closes-Bug: 1658070 ** 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/1686041 Title: Force to evacuate ACTIVE status instances failed if a host is provided Status in OpenStack Compute (nova): Fix Released Bug description: Force to evacuate ACTIVE status instances to another host(a host is provided),we can find an error 'Timeout waiting for vif plugging callback' on nova-compute log. In nova-api log,we can find network-vif-plugged event send to source compute,because nova-compute use NopClaim,not create MigrationContext,so not send this event to dest compute in function nova.compute.api._get_relevant_hosts(https://github.com/openstack/nova/blob/master/nova/compute/api.py#L4241). In https://github.com/openstack/nova/blob/master/nova/compute/manager.py#L2723, using function NopClaim when the value of scheduled_node is None while forcing evacuate ACTIVE instances to another host.(https://github.com/openstack/nova/blob/master/nova/compute/api.py#L4113) I think this is a bug. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1686041/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : [email protected] Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
