[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-8107?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14256596#comment-14256596
 ] 

ASF subversion and git services commented on CLOUDSTACK-8107:
-------------------------------------------------------------

Commit a75a43137316a60b20760aa5015d97f55520fd16 in cloudstack's branch 
refs/heads/master from [~likithas]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=a75a431 ]

CLOUDSTACK-8107. Failed to create snapshot from volume when the task is 
performed repeatedly in zone wide primary Storage.
While taking a snapshot of a volume, CS chooses the endpoint to perform backup 
snapshot operation by selecting any host that has the storage containing the 
volume mounted on it.
Instead, if the volume is attached to a VM, the endpoint chosen by CS should be 
the host that contains the VM.


> Failed to create snapshot from volume when the task is performed repeatedly 
> in zone wide primary Storage.
> ---------------------------------------------------------------------------------------------------------
>
>                 Key: CLOUDSTACK-8107
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8107
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the 
> default.) 
>    Affects Versions: 4.5.0
>            Reporter: Likitha Shetty
>            Assignee: Likitha Shetty
>            Priority: Critical
>             Fix For: Future
>
>
> +Steps to reproduce+
> 1. Setup a CS zone with a VMware DC.
> 2. Ensure the DC has 2 clusters with a host each.
> 3. Add 2 Cluster-Wide primary storage pool to each of the clusters.
> 4. Add a Zone-wide primary storage pool.
> 5. Deploy a VM with a data-disk. Ensure both the ROOT and Data disk of the VM 
> is in the zone-wide storage pool.
> 6. Take snapshots for the Data volume till the operation fails.
> In vCenter, the failure will be while Reconfiguring (worker)VM and the error 
> will be '<>.vmdk was not found'.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to