Description of problem: During live snapshot deletion on vm holding 5 disks. We see that the merge is sucessfull for 4 disks and 1 fails on engine side but completes on host side. According to vdsm.log it appears that when a Live Merge for one disk was being performed, a No such drive error was reported while checking the block job after the pivot had completed. The volume that caused this was the volume that was just pivoted from, i.e. the original active volume. However this merge completed sucessfully but caused other disk merge operation to fail on engine side but complete on host side. The images are marged illegal on rhevm database and lv's remain unremoved on Host. Issue seems similar to the bug https://bugzilla.redhat.com/show_bug.cgi?id=1447437. Opening this new bug to check further if this new bug or regression. Version-Release number of selected component (if applicable): rhevm-4.1.4.2-0.1.el7.noarch libvirt-daemon-2.0.0-10.el7_3.9.x86_64 vdsm-4.19.20-1.el7ev.x86_64 How reproducible: No Steps to Reproduce: 1. 2. 3. Actual results: "No such drive" LookupErrors occurred while checking a block job after the pivot had completed, causing the engine to "fail" merges for two other disk Expected results: Merge should complete without any errors.
according to pathces, fixes are in vdsm not engine, changing component to add to right ET.
INFO: Bug status wasn't changed from MODIFIED to ON_QA due to the following reason: [Project 'vdsm'/Component 'ovirt-engine' mismatch] For more info please contact: rhv-devops
Tested with the following code: -------------------------------- ovirt-engine-4.2.0-0.6.el7.noarch vdsm-4.20.9-1.el7ev.x86_64 Verified with the following scenario: ----------------------------------------------------- 1.Create Vm with 5 disks 2.Create snapshot s1 3.Start VM add data to disks 4.Create snapshot s2 5.Delete snapshot s1 - all snapshot is merged correctly, all disk snapshots are removed, no "No such drive error" reported Moving to VERIFIED
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://access.redhat.com/errata/RHEA-2018:1489
BZ<2>Jira Resync