Reviewed: https://review.openstack.org/499684 Committed: https://git.openstack.org/cgit/openstack/compute-hyperv/commit/?id=6e715ed580bf0f8ba5ff4c8e79b9ddba45d787c6 Submitter: Jenkins Branch: master
commit 6e715ed580bf0f8ba5ff4c8e79b9ddba45d787c6 Author: Lucian Petrut <[email protected]> Date: Thu Aug 31 18:13:49 2017 +0300 Perform proper cleanup after failed instance spawns This change ensures that vif ports as well as volume connections are properly removed after an instance fails to spawn. In order to avoid having similar issues in the future, the 'block_device_info' and 'network_info' arguments become mandatory for the VMOps.destroy method. Side note: for convenience reasons, one redundant unit test has been squashed. Closes-Bug: #1714285 Change-Id: Ifa701459b15b5a2046528fa45eca7ab382f1f7e8 ** Changed in: compute-hyperv Status: New => 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/1714285 Title: Hyper-V: leaked resources after failed spawn Status in compute-hyperv: Fix Released Status in OpenStack Compute (nova): In Progress Bug description: Volume connections as well as vif ports are not cleaned up after a failed instance spawn. To manage notifications about this bug go to: https://bugs.launchpad.net/compute-hyperv/+bug/1714285/+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
