Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1488542 - "No such drive" error on live merge of one disk causes merge of other disk to fail on engine.
"No such drive" error on live merge of one disk causes merge of other disk to...
Status: CLOSED ERRATA
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: vdsm (Show other bugs)
4.1.4
Unspecified Linux
unspecified Severity high
: ovirt-4.2.0
: ---
Assigned To: Ala Hino
Kevin Alon Goldblatt
: ZStream
Depends On:
Blocks: 1509614
  Show dependency treegraph
 
Reported: 2017-09-05 12:03 EDT by Koutuk Shukla
Modified: 2018-05-15 13:53 EDT (History)
15 users (show)

See Also:
Fixed In Version: vdsm-4.20.8
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
: 1509614 (view as bug list)
Environment:
Last Closed: 2018-05-15 13:51:57 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: Storage
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
oVirt gerrit 83490 master MERGED live-merge: Handle LookupError when tracking active layer merge job 2017-11-22 05:45 EST
oVirt gerrit 84448 master MERGED live-merge: Handle errors raised during updating VM block jobs 2017-11-21 16:13 EST
Red Hat Product Errata RHEA-2018:1489 None None None 2018-05-15 13:53 EDT

  None (edit)
Description Koutuk Shukla 2017-09-05 12:03:37 EDT
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.
Comment 16 RHV Bugzilla Automation and Verification Bot 2017-12-06 10:56:28 EST
according to pathces, fixes are in vdsm not engine, changing component to add to right ET.
Comment 17 RHV Bugzilla Automation and Verification Bot 2017-12-06 11:15:22 EST
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@redhat.com
Comment 21 Kevin Alon Goldblatt 2017-12-12 06:55:02 EST
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
Comment 26 errata-xmlrpc 2018-05-15 13:51:57 EDT
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

Note You need to log in before you can comment on or make changes to this bug.