Bug #5077
Cloned VM is not removed from vcenter datastore with Recover -> Delete if it hasn't been deployed sucessfully once
| Status: | Closed | Start date: | 03/24/2017 | |
|---|---|---|---|---|
| Priority: | Normal | Due date: | ||
| Assignee: |  Miguel Ángel Álvarez Cabrerizo | % Done: | 100% | |
| Category: | vCenter | |||
| Target version: | Release 5.4 | |||
| Resolution: | Pull request: | |||
| Affected Versions: | OpenNebula 5.2 |
Description
When a VM is deployed, a clone of a template is created and stored in the datastore. If the clone, poweron and reconfigure actions are successful the VM UUID is returned and stored in the DEPLOY_ID. If the poweron and reconfigure actions fail, no UUID is returned and if you use Recover -> Delete the VM is not found and therefore is not removed from the vcenter datastore.
Associated revisions
B #5077: Destroy VM if reconfigure or poweron actions fail in clone_vm
B #5077: Destroy VM if reconfigure or poweron actions fail in clone_vm
History
#1
Updated by Miguel Ángel Álvarez Cabrerizo over 4 years ago
- Status changed from Assigned to Closed
- % Done changed from 0 to 100
Begin, rescue blocks are added to reconfigure and poweron actions in clone_vm (vcenter_driver.rb) so the VM is destroyed once the clone has been created.
Code has been uploaded to master: 57bc086cb89297a3295b549d3d1b19b0099c2fd0
Code has been uploaded to one-5.2 branch: f548cd12a969a055d39a01e5b77e2f78a5860880