VMware: unable to delete VM with attached volumes
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Fix Released
|
High
|
Gary Kotton |
Bug Description
When the ESX running the VM's was deleted or removed the following exception occurred when the instance was deleted via OpenStack:
2015-07-02 21:33:00.638 21297 TRACE oslo.messaging.
2015-07-02 21:33:00.638 21297 TRACE oslo.messaging.
2015-07-02 21:33:00.638 21297 TRACE oslo.messaging.
2015-07-02 21:33:00.638 21297 TRACE oslo.messaging.
2015-07-02 21:33:00.638 21297 TRACE oslo.messaging.
2015-07-02 21:33:00.653 21297 ERROR oslo.messaging.
Cause: Server raised fault: 'The object has already been deleted or has not been completely created'
Faults: [ManagedObjectN
Details: {'obj': 'vm-2073'} to caller
This prevent the instance from being deleted in openstack
Changed in nova: | |
importance: | Undecided → High |
assignee: | nobody → Gary Kotton (garyk) |
tags: | added: vmware |
Changed in nova: | |
status: | New → In Progress |
Changed in nova: | |
milestone: | none → liberty-3 |
status: | Fix Committed → Fix Released |
Changed in nova: | |
milestone: | liberty-3 → 12.0.0 |
Reviewed: https:/ /review. openstack. org/198674 /git.openstack. org/cgit/ openstack/ nova/commit/ ?id=ec781596038 6ba9f522b839144 d57a423b930654
Committed: https:/
Submitter: Jenkins
Branch: master
commit ec7815960386ba9 f522b839144d57a 423b930654
Author: Gary Kotton <email address hidden>
Date: Mon Jul 6 03:57:17 2015 -0700
VMware: treat deletion exception with attached volumes
Enable the OpenStack user to successfully delete an instance that was ctNotFound.
running on an ESX that has been removed, or the instance was deleted from
the backend VC. In the event that the instance would have an attached
volume then deleting the instance would not handle the exception
ManagedObje
Change-Id: I1781256bec15ed 3301425e63c7a3d 28dc057f83e
Closes-bug: #1471751