Reviewed: https://review.openstack.org/499690 Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=761a3f4658336eba498844a6ff7586e6d2b6b7e3 Submitter: Jenkins Branch: master
commit 761a3f4658336eba498844a6ff7586e6d2b6b7e3 Author: Lucian Petrut <[email protected]> Date: Thu Aug 31 18:41:19 2017 +0300 HyperV: 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. Change-Id: I8d255658c4e45df855379738b120f0543b11027f Closes-Bug: #1714285 ** 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/1714285 Title: Hyper-V: leaked resources after failed spawn Status in compute-hyperv: Fix Released Status in OpenStack Compute (nova): Fix Released 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
