Trying to reproduce this bug using Insufficient storage domain space for cloning is incorrect. Engine UI rejects the cloning action with "low disk space" message. We need to find a way to start cloning process and then fail it somehow.
Try having more than 1 disk and 2 storage domains. Start copy and after one of them have been successfully copied, turn the source storage server off. (I have simulated this using debugger so not sure about exact reproduction steps)
Fixed. Verify version: 3.5.4-1.1.el6ev Verification procedure: 1. Add iSCSI storage domain. 2. Create VM with iSCSI disk and install OS on it. 3. Run VM and verify OS is running properly. 4. Power off VM. 5. Start cloning VM, wait two seconds after clone started and run the next command on the host for unregistering iscsi from host: iscsiadm -m node -u 6. Wait for the next failure event: "Failed to complete VM "VM-clone-name" creation and verify: Cloned VM deleted from virtual machines tab and no disks on it. Source VM still exist in virtual machines tab with disks on it. 7. Run the next command on the host for relogin iscsi to host: iscsiadm -m node -l Run source VM and verify OS is running properly (no data corruption occurred). Note: running same procedure on RHEVm 3.6 is reproducing this bug (currently this bug is in modified status), which means bug reproduction procedure for this issue is valid.
Test case created for verifying this bug: https://polarion.engineering.redhat.com/polarion/#/project/RHEVM3/workitem?id=RHEVM3-12336
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://rhn.redhat.com/errata/RHBA-2015-1725.html