Reviewed: https://review.openstack.org/277451 Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=0f8f854c2646e2e6677efdf8b1bbf82faf57f01f Submitter: Jenkins Branch: master
commit 0f8f854c2646e2e6677efdf8b1bbf82faf57f01f Author: Ludovic Beliveau <[email protected]> Date: Mon Feb 8 10:36:30 2016 -0500 Failed migration shoudn't be reported as in progress This fix add 'failed' status to the list of filters for migrations that are reported by migration_get_in_progress_by_host_and_node. Change-Id: I7de143d73a84339d2184d09e5907cbbe941a2e66 Closes-Bug: #1543123 ** 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/1543123 Title: PCI device not freed on failed migration Status in OpenStack Compute (nova): Fix Released Bug description: But found in latest master. It has been observed that a failed cold migration for an instance with PCI devices cause those PCI devices to not be freed (still in used) by the PciDevTracker. The audit task (ResourceTracker.update_available_resource) gets the list of in progress migration (from migration_get_in_progress_by_host_and_node) and attempt to clean the allocation of PCI devices (PciDevTracker.clean_usage). In this case PCI devices that are not part of any migration are freed up and put back in the pool of available PCI devices. The problem is that migration_get_in_progress_by_host_and_node only filters out migration in state ['confirmed', 'reverted', 'error']. Migration is state 'failed' are reported as in progress. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1543123/+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
