Description of problem: Snapshot remains locked after failed live merge due to restart of vdsm Version-Release number of selected component (if applicable): Verified with the following code: ------------------------------------------------------------- ovirt-engine-4.1.3.4-0.1.el7.noarch rhevm-4.1.3.4-0.1.el7.noarch vdsm-4.19.19-1.el7ev.x86_64 How reproducible: Every time Verified with the the following scenario: ------------------------------------------------------------ 1. Create VM_14 with 5 disks , thin and preallocated, block and nfs 2. Create 3 snapshots, sna1, sna2, sna3 3. Start the snapshot vm22 4. Delete sna2 and a few seconds later restart the vdsm on the host . The delete fails of the snapshot fails and the snapshot sna2 remains in a locked state Actual results: The delete fails of the snapshot fails and the snapshot sna2 remains in a locked state Expected results: When the vdsm comes up again the snapshot should be in a normal state and allow a retry of the delete Additional info:
Created attachment 1290772 [details] server, engine, vdsm logs Adding logs
*** Bug 1464213 has been marked as a duplicate of this bug. ***
Kevin, is there any difference between this bug and 1464218 besides the versions used?
(In reply to Kevin Alon Goldblatt from comment #0) > Description of problem: > Snapshot remains locked after failed live merge due to restart of vdsm > > Version-Release number of selected component (if applicable): > > Verified with the following code: > ------------------------------------------------------------- > ovirt-engine-4.1.3.4-0.1.el7.noarch > rhevm-4.1.3.4-0.1.el7.noarch > vdsm-4.19.19-1.el7ev.x86_64 > > > How reproducible: > Every time > > Verified with the the following scenario: > ------------------------------------------------------------ > 1. Create VM_14 with 5 disks , thin and preallocated, block and nfs > 2. Create 3 snapshots, sna1, sna2, sna3 > 3. Start VM vm22 > 4. Delete sna2 and a few seconds later restart the vdsm on the host . The > delete of the snapshot fails and the snapshot sna2 remains in a locked > state > > > > Actual results: > The of the snapshot fails and snapshot sna2 remains in a > locked state > > > Expected results: > When the vdsm comes up again the snapshot should be in a normal state and > allow a retry of the delete > > > Additional info:
(In reply to Allon Mureinik from comment #3) > Kevin, is there any difference between this bug and 1464218 besides the > versions used? The same problem happens on both version 4.1.3 and 4.2. I tested both versions
In that case I'm targeting the other bug to 4.1.3 and closing this one as a duplicate, when we have a zstream bug we fix it for master as well anyway *** This bug has been marked as a duplicate of bug 1464218 ***