Red Hat Bugzilla – Bug 885489
3.2 Error deleting VM disk
Last modified: 2016-02-10 14:43:51 EST
Description of problem:
Attempted to remove powered-off VM. Manger reports "Failed to remove VM <name>."
The logical volume containing the actual disk image (/dev/c294c8b1-b2e7-4564-bbb2-2d6c1f54b895/38c6b100-31f8-4914-a760-eb1c5e15cce4) *has* been removed, but the disk still shows up in the manager.
Version-Release number of selected component (if applicable):
Not 100%, but this is the second time I have seen this problem.
Steps to Reproduce:
1. Create VM with at least one disk.
2. Run VM fora while?
3. Attempt to remove VM.
VM (and disk) should be deleted.
Created attachment 660406 [details]
/var/log/ovirt-engine/engine.log (from RHEV manager)
Created attachment 660407 [details]
/var/log/vdsm/vdsm.log (from hypervisor 1 of 2)
Created attachment 660408 [details]
/var/log/vdsm/vdsm.log (from hypervisor 2 of 2)
This bug might be a duplicate of a bug I've opened that requires a fix in vdsm -
lease files are not removed when removing volumes in file SDs v3:
It is not certain because there's a minor problem with the logging that Eduardo is currently fixing.
Anyway, what probably happens is that the image directory is not empty because of failed previous deletion of a volume(probably remaining lease file) and now the directory is not empty and can't be removed.
The log fix:
I assume from the log, that engine side worked as suspected (VM was able to start after the remove failed).
Since the exception of deletion was generated from VDSM, moving the bug to VDSM component.
Please close as duplicate or move to ON_QA, if you think that the change-id is already fixing it
Yeela, is this a duplicate? iirc in the end you said that the code paths are different because in your use case we don't reach the faulty logging line?
*** Bug 885794 has been marked as a duplicate of this bug. ***
*** Bug 890826 has been marked as a duplicate of this bug. ***
*** Bug 891068 has been marked as a duplicate of this bug. ***
vdsm-4.10.2-7.0. was unable to reproduce with several VMs ,several disk types.
VMs with the disks were successfully deleted.
3.2 has been released