Bug 1540351

Summary: VM disk migration to another storage domain (NFS), resulted only moving one image and src images getting deleted.
Product: Red Hat Enterprise Virtualization Manager Reporter: Bimal Chollera <bcholler>
Component: vdsmAssignee: Fred Rolland <frolland>
Status: CLOSED DUPLICATE QA Contact: Raz Tamir <ratamir>
Severity: high Docs Contact:
Priority: unspecified    
Version: 4.1.7CC: amureini, bazulay, ebenahar, frolland, lsurette, mkalinin, srevivo, ycui, ykaul
Target Milestone: ovirt-4.1.10Flags: lsvaty: testing_plan_complete-
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: 2018-02-07 16:33:32 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:
Bug Depends On:    
Bug Blocks: 1540310    

Description Bimal Chollera 2018-01-30 20:17:40 UTC
Description of problem:

VM disk contained 2 images.  Base and Active/LEAF.  Only the base image appears to have migrated to the dst SD and no indication that Active/LEAF move was initiated.  Once the COPY task was deemed successful, the source images were purged which included the Active/LEAF that wasn't moved.  This rendered VM not to boot and missing data.

Error reported in vdsm.log:

~~~
VolumeDoesNotExist: Volume does not exist: (u'2ad59faa-c5c9-489f-a179-5e2c8a382c9a',)
~~~

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


rhevm-4.0.7.4-0.1.el7ev.noarch

Red Hat Virtualization Host 4.0 (el7.2)
vdsm-4.18.13-1.el7ev.x86_64

NFS - File based storage.


How reproducible:

Not reproducible, but occurred on end-user system.

Steps to Reproduce:
1.
2.
3.

Actual results:

Active/LEAF image was not migrated and source SD images were purged.

Expected results:

Disk migration of all images should move before purging the source SD images.

Additional info:

Comment 4 Fred Rolland 2018-02-04 09:19:06 UTC
Seems a duplicate of 1538840

Comment 5 Allon Mureinik 2018-02-07 16:33:32 UTC

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

Comment 6 Fred Rolland 2018-02-08 13:05:34 UTC
I will look at this one again to make sure this is really the same as #1538840

Comment 7 Franta Kust 2019-05-16 12:54:44 UTC
BZ<2>Jira re-sync