Bug 1509614 - [downstream clone - 4.1.8] "No such drive" error on live merge of one disk causes merge of other disk to fail on engine.
Summary: [downstream clone - 4.1.8] "No such drive" error on live merge of one disk ca...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: vdsm
Version: 4.1.4
Hardware: Unspecified
OS: Linux
unspecified
high
Target Milestone: ovirt-4.1.8
: ---
Assignee: Ala Hino
QA Contact: Kevin Alon Goldblatt
URL:
Whiteboard:
Depends On: 1488542
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-11-05 07:38 UTC by rhev-integ
Modified: 2021-03-11 17:58 UTC (History)
17 users (show)

Fixed In Version: vdsm v4.19.40
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1488542
Environment:
Last Closed: 2017-12-12 09:24:07 UTC
oVirt Team: Storage
Target Upstream Version:
Embargoed:
lsvaty: testing_plan_complete-


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHEA-2017:3428 0 normal SHIPPED_LIVE VDSM bug fix and enhancement update 4.1.8 2017-12-12 14:16:56 UTC
oVirt gerrit 83490 0 master MERGED live-merge: Handle LookupError when tracking active layer merge job 2020-07-22 15:00:32 UTC
oVirt gerrit 84473 0 ovirt-4.1 MERGED live-merge: Handle errors raised during updating VM block jobs 2020-07-22 15:00:31 UTC
oVirt gerrit 84516 0 ovirt-4.1 MERGED live-merge: Handle LookupError when tracking active layer merge job 2020-07-22 15:00:31 UTC

Description rhev-integ 2017-11-05 07:38:44 UTC
+++ This bug is a downstream clone. The original bug is: +++
+++   bug 1488542 +++
======================================================================

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.

(Originally by Koutuk Shukla)

Comment 18 Kevin Alon Goldblatt 2017-12-04 18:23:19 UTC
Verified with the following code:
----------------------------------------
ovirt-engine-4.1.8.2-0.1.el7.noarch
vdsm-4.19.41-1.el7ev.x86_64

Verified with the following scenario:
----------------------------------------
1. Created a vm with at least 10 disks
2. Start the vm and write to all disks
3. Create snapshot
4. Delete snapshot >>>>> successful delete , no Drive not found errors


Moving to VERIFIED

Comment 21 errata-xmlrpc 2017-12-12 09:24:07 UTC
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-2017:3428

Comment 22 Daniel Gur 2019-08-28 13:15:08 UTC
sync2jira

Comment 23 Daniel Gur 2019-08-28 13:20:11 UTC
sync2jira


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