Red Hat Bugzilla – Bug 820645
wrong order in moving storage
Last modified: 2016-02-10 12:08:41 EST
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
virtual machine not bootable anymore (Exit message Bad volume specification)
virtual machine boots from new storage
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)
Created attachment 583605 [details]
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.
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.
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 ***