Bug 1668366

Summary: After Snapshot disk download TeardownImageVDSCommand attempts to deactivate the in-use LV's.
Product: Red Hat Enterprise Virtualization Manager Reporter: Koutuk Shukla <kshukla>
Component: ovirt-engineAssignee: Fedor Gavrilov <fgavrilo>
Status: CLOSED DUPLICATE QA Contact: meital avital <mavital>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 4.2.7CC: eshenitz, frolland, rbarry, Rhev-m-bugs, tnisan
Target Milestone: ovirt-4.4.0Flags: lsvaty: testing_plan_complete-
Target Release: 4.3.0   
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: 2019-09-12 06:32:07 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 Koutuk Shukla 2019-01-22 14:39:39 UTC 
Description of problem:

After using the  python script /usr/share/doc/python-ovirt-engine-sdk4-4.2.9/examples/download_disk_snapshots.py   to download the Snapshot disk from VM. TeardownImageVDSCommand attempts to deactivate the in-use LV's of VM.  This attempt fails if the Host running VM is used to perform the download disk task. 

Version-Release number of selected component (if applicable):
Red Hat Virtualization 4.2.7

How reproducible:
100%

Actual results:

-- TeardownImageVDSCommand works fine if the Host not running the VM is selected to perform download disk. But if the Host running the VM is selected the TeardownImageVDSCommand fails.

-- This does not block the actual download of the disk but just throws an error like below.

"Failed to tear down image disk-name after image transfer session"

Expected results:

-- Unsure if TeardownImageVDSCommand is required if downloading a snapshot disk.
Comment 5 Daniel Gur 2019-08-28 13:14:11 UTC 
sync2jira
Comment 6 Daniel Gur 2019-08-28 13:18:27 UTC 
sync2jira
Comment 7 Eyal Shenitzky 2019-09-12 06:32:07 UTC 

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