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/13 20:37:20 UTC
[jira] [Updated] (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:all-tabpanel ]
Fang Wang updated CLOUDSTACK-2904:
----------------------------------
Priority: Critical (was: Major)
> 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