You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cloudstack.apache.org by "Animesh Chaturvedi (JIRA)" <ji...@apache.org> on 2013/07/24 00:56:50 UTC
[jira] [Updated] (CLOUDSTACK-3665) Failed to create volume from
snapshot
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3665?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Animesh Chaturvedi updated CLOUDSTACK-3665:
-------------------------------------------
Component/s: XenServer
> Failed to create volume from snapshot
> -------------------------------------
>
> Key: CLOUDSTACK-3665
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3665
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the default.)
> Components: Storage Controller, VMware, XenServer
> Affects Versions: 4.2.0
> Reporter: Sailaja Mada
> Priority: Critical
> Fix For: 4.2.0
>
> Attachments: apilog.log, cloud-backup.dmp, management-server.log
>
>
> Steps:
> 1. Configure Adv zone with VMWARE with Zone wide primary storage
> 2. Deploy VM using default template
> 3. Create Snapshot from ROOT volume
> 4. Tried to create volume from thos snapshot .
> Observation:
> It failed to create volume from snapshot saying Storage is unavailable. But storage is available and i was able to create and attach DATA volumes to the instance. Only while creating volume from snapshot this failure is observed (Attached logs and DB)
> 2013-07-19 16:20:15,918 INFO [cloud.storage.VolumeManagerImpl] (Job-Executor-30:job-46 = [ 8d88b415-e4e5-453e-865d-48c37a640e7b ]) There are no available storage pools to store the volume in
> 2013-07-19 16:20:15,919 DEBUG [cloud.storage.VolumeManagerImpl] (Job-Executor-30:job-46 = [ 8d88b415-e4e5-453e-865d-48c37a640e7b ]) Failed to create volume: 14
> 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:558)
> at com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
> at com.cloud.storage.VolumeManagerImpl.createVolumeFromSnapshot(VolumeManagerImpl.java:614)
> at com.cloud.storage.VolumeManagerImpl.createVolume(VolumeManagerImpl.java:1072)
> 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:189)
> at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:158)
> at com.cloud.async.AsyncJobManagerImpl$1.run(AsyncJobManagerImpl.java:531)
> 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:1110)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
> at java.lang.Thread.run(Thread.java:679)
> 2013-07-19 16:20:15,983 DEBUG [cloud.async.AsyncJobManagerImpl] (Job-Executor-30:job-46 = [ 8d88b415-e4e5-453e-865d-48c37a640e7b ]) Complete async job-46 = [ 8d88b415-e4e5-453e-865d-48c37a640e7b ], jobStatus: 2, resultCode: 530, result: Error Code: 530 Error text: Failed to create a volume
> 2013-07-19 16:20:17,115 DEBUG [storage.secondary.SecondaryStorageManagerImpl] (secstorage-1:null) Zone 1 is ready to launch secondary storage VM
--
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