Bug 1899360

Summary:	When performing multiple LSM, some disk moves do not finish as expected
Product:	Red Hat Enterprise Virtualization Manager	Reporter:	Marcus West <mwest>
Component:	vdsm	Assignee:	Benny Zlotnik <bzlotnik>
Status:	CLOSED DUPLICATE	QA Contact:	Avihai <aefrat>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	4.4.1	CC:	bcholler, bzlotnik, eshenitz, gveitmic, lsurette, mavital, mkalinin, srevivo, tnisan, ycui
Target Milestone:	ovirt-4.4.4-2	Keywords:	ZStream
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2021-03-14 06:40:08 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	Storage	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Marcus West 2020-11-18 23:57:57 UTC

## Description of problem:

When performing simultaneous Live Storage Migration, deleting source disk fails

## Version-Release number of selected component (if applicable):

ovirt-engine-4.4.2.6-0.2.el8ev.noarch
rhvh--4.4.1.1--0.20200722.0
vdsm-4.40.22-1.el8ev.x86_64
qemu-img-4.2.0-29.module+el8.2.1+7297+a825794d.x86_64
qemu-kvm-4.2.0-29.module+el8.2.1+7297+a825794d.x86_64
libvirt-6.0.0-25.module+el8.2.1+7154+47ffd890.x86_64

## How reproducible:

sometimes (still testing)

## Steps to Reproduce:
1. Got to Disk tab
2. select multiple disk
3. select 'Move'

## Actual results:

Engine reports 'Possible failure while deleting <Disk Alias> from the source Storage Domain <SD>'.  VM process has both source and destination disks open, although the LV's appear to be removed for the source (both still appear in 'dmsetup' output).  It's unclear how to recover the VM in this situation.

## Expected results:

Move disks from on SD to another without issue.

## Additional info:

Comment 11 Eyal Shenitzky 2021-03-14 06:40:08 UTC

Thanks, Germano, Bimal, and Marcus.
Closing this bug as a duplication according to your comments.

*** This bug has been marked as a duplicate of bug 1833780 ***