You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cloudstack.apache.org by "Fang Wang (JIRA)" <ji...@apache.org> on 2013/06/27 00:32:20 UTC
[jira] [Commented] (CLOUDSTACK-2904) After volume migration on
Vmware, taking a snapshot, and then volume migration fails on this new
volume
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2904?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13694317#comment-13694317 ]
Fang Wang commented on CLOUDSTACK-2904:
---------------------------------------
step1:
before taking the snapshot on the migrated vol:
[root@nfs2 primary2]# cd i-2-10-VM/
[root@nfs2 i-2-10-VM]# ls -lt
total 1394692
-rw------- 1 root root 67117056 Jun 26 15:08 ROOT-10-15-000001-delta.vmdk
-rw------- 1 root root 322 Jun 13 16:27 ROOT-10-15-000001.vmdk
-rw------- 1 root root 201334784 Jun 13 16:27 ROOT-10-15-delta.vmdk
-rw------- 1 root root 337 Jun 13 15:02 ROOT-10-15.vmdk
-rw------- 1 root root 517 Jun 13 15:02 657640660f7a36b6a839e90dc1c8e74b.vmdk
-rw------- 1 root root 2147483648 Jun 13 15:02 657640660f7a36b6a839e90dc1c8e74b-flat.vmdk
step 2, take a snapshot,
after the snapshot is taken:
[root@nfs2 primary2]# cd i-2-10-VM/
[root@nfs2 i-2-10-VM]# ls -lt
total 1244596
-rw------- 1 root root 67117056 Jun 26 15:26 ROOT-10-15-000001-delta.vmdk
-rw------- 1 root root 367 Jun 26 15:15 ROOT-10-15-000001.vmdk
-rw------- 1 root root 2147483648 Jun 26 15:15 657640660f7a36b6a839e90dc1c8e74b-flat.vmdk
-rw------- 1 root root 517 Jun 26 15:15 657640660f7a36b6a839e90dc1c8e74b.vmdk
[root@nfs2 i-2-10-VM]#
step 3: migrate the vol, the vol of the snpshot:
migrate from primary2 ---> primary1, UI specify the only available storage is primary1, click ok;
the vol still stays at the primary2 storage, though it says "task complete". check the contents, it still stays at primary2.
The rror scenerio is different from what I saw before: it silently completes the task, but did not carry it out. instead of an exception
> After volume migration on Vmware, taking a snapshot, and then volume migration fails on this new volume
> -------------------------------------------------------------------------------------------------------
>
> Key: CLOUDSTACK-2904
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2904
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the default.)
> Environment: master build, or vmware-storage-migration branch with Vmware host
> Reporter: Fang Wang
> Assignee: Fang Wang
> Priority: Critical
>
> Create a simple VM with a root volume.
> Migrate the root volume to another primary storage.
> we see four vmdk files getting created in the VM folder on the new primary.
> Two are uuid-delta.vmdk and uuid.vmdk style files. The other two are the ROOT-x-y-delta.vmdk and ROOT-x-y.vmdk files.
> take a snapshot of the root volume via the cloudstack GUI. What we see is that the ROOT-x-y* files are getting deleted from the VM folder in the new primary. Additionally, the VM’s root disk is getting changed to the other uuid.vmdk file.
> when we now attempt to migrate this volume again, it will fail saying that it cannot find the ROOT-x-y disk.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira