cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Animesh Chaturvedi (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (CLOUDSTACK-2904) After volume migration on Vmware, taking a snapshot, and then volume migration fails on this new volume
Date Thu, 01 Aug 2013 23:55:50 GMT

     [ https://issues.apache.org/jira/browse/CLOUDSTACK-2904?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Animesh Chaturvedi updated CLOUDSTACK-2904:
-------------------------------------------

    Fix Version/s: 4.2.0
    
> 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.) 
>          Components: Volumes
>    Affects Versions: 4.2.0
>         Environment: master build, or vmware-storage-migration branch with Vmware host
>            Reporter: Fang Wang
>            Priority: Critical
>             Fix For: 4.2.0
>
>
> 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

Mime
View raw message