Red Hat Bugzilla – Bug 1279354
Rollback of RHEV VM fails if disks aren't completely created yet
Last modified: 2017-01-12 14:14:47 EST
Description of problem:
When there is an error and the creation of a VM on RHEV needs to be rolled back, Satellite attempts to do this, but fails if the disks for the VM haven't been completely created yet.
My storage is slow, so I have this happen all the time, but if you would create a VM on fast storage with large preallocated disks, I can imagine this happening too.
Failed to destroy a compute RHEV (RHEV) instance rhev-test-01.vm.thuisnet.lan: Cannot remove VM: The following disks are locked: rhev-test-01-vm-thuisnet-lan_Disk1. Please try again in a few minutes.
Not sure whether to file this as RHEV or Satellite bug, tbh.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Fill in 'New host' page to deploy on RHEV
2. Make intentional error in IP address for example
VM is created, but roll back fails: VM is not removed due to the above error
VM is created, and roll back (VM removal) succeeds
Either Satellite needs to retry if this happens, or RHEV needs to be able to schedule the deletion for after the disks are created.
Per 6.3 planning, moving out non acked bugs to the backlog
This is an older bug which I do not envision being addressed in the near term. I am closing this out. If you believe doing so is an issue, please feel free to re-open and provide additional business information. Thank you.