Bug 820645

Summary: wrong order in moving storage
Product: Red Hat Enterprise Virtualization Manager Reporter: Pieter Vogel <pvogel>
Component: vdsmAssignee: Ayal Baron <abaron>
Status: CLOSED DUPLICATE QA Contact: Haim <hateya>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: unspecifiedCC: abaron, amureini, bazulay, danken, hateya, iheim, lpeer, yeylon, ykaul
Target Milestone: ---   
Target Release: 3.3.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: storage
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-02-16 20:36:17 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:
Attachments:
Description Flags
the move process out of the vdsm.log
none
complete log none

Description Pieter Vogel 2012-05-10 15:03:34 UTC
Created attachment 583603 [details]
the move process out of the vdsm.log

Description of problem:
virtual machine with two disks in rhev (which I migrated from 2.2 to 3.0) Machine is in 3.0 hypervisor but storage was on old domain. After starting a storage move in webadmin it failed. (hypervisor crashed) Virtual machine was not bootable anymore.

It was not bootable because:
1 disk one is correctly moved
2 disk two is correctly moved
3 old disk1 is zero-ed
4 crash (I don't know why this happened but that is not important for this bug) 
5 virtual machine is still pointing to old disk location which does not exist anymore.

Version-Release number of selected component (if applicable):
rhev2.2 and rhev3.0 which rhev3.0 manager

  
Actual results:
virtual machine not bootable anymore (Exit message Bad volume specification)

Expected results:
virtual machine boots from new storage

Additional info:
after step 2 rhev should first point virtual machine to new storage location and then it may start writing zero's to old disk.

I fixed my machine by editing machine info in rhevm-database and then starting the virtual machine. That worked because moving storage did finish correct. writing zeros failed. (or it failed shortly after writing zeros)

Comment 1 Pieter Vogel 2012-05-10 15:05:43 UTC
Created attachment 583605 [details]
complete log

Comment 3 RHEL Program Management 2012-05-14 04:04:44 UTC
This request was not resolved in time for the current release.
Red Hat invites you to ask your support representative to
propose this request, if still desired, for consideration in
the next release of Red Hat Enterprise Linux.

Comment 5 RHEL Program Management 2012-07-10 08:55:13 UTC
This request was not resolved in time for the current release.
Red Hat invites you to ask your support representative to
propose this request, if still desired, for consideration in
the next release of Red Hat Enterprise Linux.

Comment 6 RHEL Program Management 2012-07-11 01:55:50 UTC
This request was erroneously removed from consideration in Red Hat Enterprise Linux 6.4, which is currently under development.  This request will be evaluated for inclusion in Red Hat Enterprise Linux 6.4.

Comment 7 RHEL Program Management 2012-12-14 08:54:09 UTC
This request was not resolved in time for the current release.
Red Hat invites you to ask your support representative to
propose this request, if still desired, for consideration in
the next release of Red Hat Enterprise Linux.

Comment 8 Ayal Baron 2013-02-16 20:36:17 UTC
rhev 3.1 supports disks on different storage domains so this should be better now (many things have been fixed).
But the real solution for this is splitting move into copy and delete.

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