[
https://issues.apache.org/jira/browse/CLOUDSTACK-4251?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
prashant kumar mishra updated CLOUDSTACK-4251:
----------------------------------------------
Summary: attach volume to instance(startvm=false) fail; Unable to find
storage pool when create volumetry (was: attach volume to
instance(startvm=false) fail; Unexpected exception while executing
org.apache.cloudstack.api.command.user.volume.AttachVolumeCmd
com.cloud.utils.exception.CloudRuntimeException: Unable to find storage pool
when create volumetry)
> attach volume to instance(startvm=false) fail; Unable to find storage pool
> when create volumetry
> ------------------------------------------------------------------------------------------------
>
> Key: CLOUDSTACK-4251
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4251
> 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: Hypervisore:xenserver 6.1
> Reporter: prashant kumar mishra
> Fix For: 4.2.0
>
>
> Steps to reproduce
> -------------------------------
> 1) DeployVm using api, append startVm=false to the command
> 2) Create a new dataDisk
> 3) Attach the datadisk to the vm
> Actual
> -----------
> attache volume to stop vm is failing
> My observation
> ----------------------
> 1-when i started the vm(vm deployed with startVm=false) ,able to attache
> volume
> 2-Did a start stop on vm(vm deployed with startVm=false), was able to
> attache volume
> 3-did not see issue with vms deployed through UI.
> logs
> -------
> 2013-08-12 21:20:19,499 DEBUG
> [storage.allocator.ClusterScopeStoragePoolAllocator] (Job-Executor-37:job-37
> = [ ed91f71f-335c-43b9-b6e9-2b4060adeab7 ]) ClusterScopeStoragePoolAllocator
> looking for storage pool
> 2013-08-12 21:20:19,499 WARN [cloud.storage.VolumeManagerImpl]
> (Job-Executor-37:job-37 = [ ed91f71f-335c-43b9-b6e9-2b4060adeab7 ]) Unable to
> find storage pool when create volume try
> 2013-08-12 21:20:19,526 ERROR [cloud.async.AsyncJobManagerImpl]
> (Job-Executor-37:job-37 = [ ed91f71f-335c-43b9-b6e9-2b4060adeab7 ])
> Unexpected exception while executing
> org.apache.cloudstack.api.command.user.volume.AttachVolumeCmd
> com.cloud.utils.exception.CloudRuntimeException: Unable to find storage pool
> when create volumetry
> at
> com.cloud.storage.VolumeManagerImpl.createVolume(VolumeManagerImpl.java:677)
> at
> com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
> at
> com.cloud.storage.VolumeManagerImpl.createVolumeOnPrimaryStorage(VolumeManagerImpl.java:1538)
> at
> com.cloud.storage.VolumeManagerImpl.attachVolumeToVM(VolumeManagerImpl.java:1840)
> at
> com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
> at
> org.apache.cloudstack.api.command.user.volume.AttachVolumeCmd.execute(AttachVolumeCmd.java:122)
> 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-08-12 21:20:19,530 DEBUG [cloud.async.AsyncJobManagerImpl]
> (Job-Executor-37:job-37 = [ ed91f71f-335c-43b9-b6e9-2b4060adeab7 ]) Complete
> async job-37 = [ ed91f71f-335c-43b9-b6e9-2b4060adeab7 ], jobStatus: 2,
> resultCode: 530, result: Error Code: 530 Error text: Unable to find storage
> pool when create volumetry
> 2013-08-12 21:20:19,923 DEBUG [cloud.consoleproxy.ConsoleProxyManagerImpl]
> (consoleproxy-1:null)
--
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
