[
https://issues.apache.org/jira/browse/CLOUDSTACK-3758?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13717953#comment-13717953
]
Sateesh Chodapuneedi commented on CLOUDSTACK-3758:
--------------------------------------------------
3665 looked different issue as Sanjeev and Manasa has reported the same issue
observed in xenserver as well.
This bug is specific to zone wide primary storage and xenserver doesn't support
that feature.
> [Vmware][ZWPS] Failed to create volume from snapshot
> ----------------------------------------------------
>
> Key: CLOUDSTACK-3758
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3758
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Storage Controller, VMware
> Affects Versions: 4.2.0
> Reporter: Sateesh Chodapuneedi
> Assignee: Sateesh Chodapuneedi
> Priority: Critical
> Fix For: 4.2.0
>
>
> 1) Deployed advanced zone over VMware with primary storage pool with scope
> 'ZONE'
> 2) Created user instance
> 3) Created snapshot of root volume of the instance using UI.
> 4) Attempted to create volume from the above snapshot. This failed.
> 2013-07-24 01:24:42,325 DEBUG [cloud.storage.VolumeManagerImpl]
> (Job-Executor-1:job-19 = [ 40c07491-6796-43fb-a1e0-36716a592d4b ]
> ctx-10bef771) Failed to create volume: 8
> com.cloud.exception.StorageUnavailableException: Resource [StoragePool:-1] is
> unreachable: There are no available storage pools to store the volume in
> at
> com.cloud.storage.VolumeManagerImpl.createVolumeFromSnapshot(VolumeManagerImpl.java:555)
> at
> com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
> at
> com.cloud.storage.VolumeManagerImpl.createVolumeFromSnapshot(VolumeManagerImpl.java:611)
> at
> com.cloud.storage.VolumeManagerImpl.createVolume(VolumeManagerImpl.java:1069)
> at
> com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
> at
> com.cloud.storage.VolumeManagerImpl.createVolume(VolumeManagerImpl.java:188)
> at
> org.apache.cloudstack.api.command.user.volume.CreateVolumeCmd.execute(CreateVolumeCmd.java:190)
> at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:158)
> at com.cloud.async.AsyncJobManagerImpl$1.run(AsyncJobManagerImpl.java:538)
> at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
> at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
> at java.util.concurrent.FutureTask.run(FutureTask.java:166)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1146)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
> at java.lang.Thread.run(Thread.java:679)
> 2013-07-24 01:24:42,355 DEBUG [cloud.async.AsyncJobManagerImpl]
> (Job-Executor-1:job-19 = [ 40c07491-6796-43fb-a1e0-36716a592d4b ]) Complete
> async job-19 = [ 40c07491-6796-43fb-a1e0-36716a592d4b ], jobStatus: 2,
> resultCode: 530, result: Error Code: 530 Error text: Failed to create a volume
--
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
