You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cloudstack.apache.org by "Chip Childers (JIRA)" <ji...@apache.org> on 2013/06/04 20:55:29 UTC

[jira] [Updated] (CLOUDSTACK-1352) KVM 6.3 snapshot - when snapshot of ROOT volume is being created, snapshot of data volume remains in Creating state

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

Chip Childers updated CLOUDSTACK-1352:
--------------------------------------

    Fix Version/s:     (was: 4.1.0)
                   4.2.0
    
> KVM 6.3 snapshot - when snapshot of ROOT volume is being created, snapshot of data volume remains in Creating state
> -------------------------------------------------------------------------------------------------------------------
>
>                 Key: CLOUDSTACK-1352
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1352
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: Management Server, Storage Controller
>    Affects Versions: 4.1.0
>         Environment: MS  rhel 6.3   latest build   2/20/2013
> host rhel 6.3  KVM
>            Reporter: angeline shen
>            Assignee: Venkata Siva Vijayendra Bhamidipati
>             Fix For: 4.2.0
>
>
> MS  rhel 6.3   latest build   2/20/2013
> host rhel 6.3  KVM   latest build   2/20/2013   
> 1. advance zone.  VPC :   VPC network:  create VMs
> 2. while  snapshot of ROOT volume  is being taken, take snapshot of DATA volume 
> Result:   Error dialog:
> There is other active snapshot tasks on the instance to which the volume is attached, please try again later
> snapshot of data volume remains in Creating state but is deletable.
> This behavior is different than Cloudplatform where snapshot of ROOT volume and DATA volume can be 
> taken simultaneously.

--
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