You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cloudstack.apache.org by "Chandan Purushothama (JIRA)" <ji...@apache.org> on 2013/07/24 00:24:48 UTC
[jira] [Reopened] (CLOUDSTACK-3493) Attach volume to VM is failing
in case of Primary-Localstorage .
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3493?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Chandan Purushothama reopened CLOUDSTACK-3493:
----------------------------------------------
Koushik,
May I know why cannot the User deploy a VM with local storage service offering with root disk on the Local storage and Data disks on the shared Storage. This behavior was supported in previous releases,
Thank you,
Chandan.
> Attach volume to VM is failing in case of Primary-Localstorage .
> ----------------------------------------------------------------
>
> Key: CLOUDSTACK-3493
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3493
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the default.)
> Components: Management Server
> Affects Versions: 4.2.0
> Environment: 4.2 stable build
> Reporter: manasaveloori
> Assignee: Koushik Das
> Priority: Blocker
> Fix For: 4.2.0
>
> Attachments: management-server.zip
>
>
> 1. Create advanced zone 1 with Primary-LocalStorage Secondary-NFS Host-Xen.(System VMs not in local storage)
> 2. Deploy a VM with default template.
> 3. Create a Volume.
> 4. Attach the created volume to the VM.
> Observed the following exception :
> 2013-07-12 19:24:30,025 DEBUG [cloud.async.AsyncJobManagerImpl] (catalina-exec-17:null) submit async job-96, details: AsyncJobVO {id:96, userId: 2, accountId: 2, sessionKey: null, instanceType: Volume, instanceId: 33, cmd: org.apache.cloudstack.api.command.user.volume.AttachVolumeCmd, cmdOriginator: null, cmdInfo: {"response":"json","id":"2d279447-7d91-4b97-9c86-10f09d08771c","sessionkey":"NPIr/lm7+u0dB9XxfOmuCTTHu+8\u003d","cmdEventType":"VOLUME.ATTACH","ctxUserId":"2","virtualMachineId":"924eb3a7-321a-432d-8ba8-e7c8cfeee87f","httpmethod":"GET","_":"1373617816676","ctxAccountId":"2","ctxStartEventId":"389"}, cmdVersion: 0, callbackType: 0, callbackAddress: null, status: 0, processStatus: 0, resultCode: 0, result: null, initMsid: 6805241462820, completeMsid: null, lastUpdated: null, lastPolled: null, created: null}
> 2013-07-12 19:24:30,029 DEBUG [cloud.api.ApiServlet] (catalina-exec-17:null) ===END=== 10.252.192.69 -- GET command=attachVolume&id=2d279447-7d91-4b97-9c86-10f09d08771c&virtualMachineId=924eb3a7-321a-432d-8ba8-e7c8cfeee87f&response=json&sessionkey=NPIr%2Flm7%2Bu0dB9XxfOmuCTTHu%2B8%3D&_=1373617816676
> 2013-07-12 19:24:30,033 DEBUG [cloud.async.AsyncJobManagerImpl] (Job-Executor-10:job-96) Executing org.apache.cloudstack.api.command.user.volume.AttachVolumeCmd for job-96
> 2013-07-12 19:24:30,153 ERROR [cloud.async.AsyncJobManagerImpl] (Job-Executor-10:job-96) Unexpected exception while executing org.apache.cloudstack.api.command.user.volume.AttachVolumeCmd
> com.cloud.utils.exception.CloudRuntimeException: Can't move volume between scope: CLUSTER and HOST
> at com.cloud.storage.VolumeManagerImpl.needMoveVolume(VolumeManagerImpl.java:1586)
> at com.cloud.storage.VolumeManagerImpl.attachVolumeToVM(VolumeManagerImpl.java:1839)
> 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:155)
> at com.cloud.async.AsyncJobManagerImpl$1.run(AsyncJobManagerImpl.java:513)
> 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-12 19:24:30,155 DEBUG [cloud.async.AsyncJobManagerImpl] (Job-Executor-10:job-96) Complete async job-96, jobStatus: 2, resultCode: 530, result: Error Code: 530 Error text: Can't move volume between scope: CLUSTER and HOST
> 2013-07-12 19:24:33,092 DEBUG [cloud.api.ApiServlet] (catalina-exec-13:null) ===START=== 10.252.192.69 -- GET command=queryAsyncJobResult&jobId=81574554-3985-4738-9085-576c65391e44&response=json&sessionkey=NPIr%2Flm7%2Bu0dB9XxfOmuCTTHu%2B8%3D&_=1373617819883
> 2013-07-12 19:24:33,097 DEBUG [agent.manager.DirectAgentAttache] (DirectAgent-37:null) Ping from 1
> 2013-07-12 19:24:33,118 DEBUG [cloud.async.AsyncJobManagerImpl] (catalina-exec-13:null) Async job-96 completed
> 2013-07-12 19:24:33,129 DEBUG [cloud.api.ApiServlet] (catalina-exec-13:null) ===END=== 10.252.192.69 -- GET command=queryAsyncJobResult&jobId=81574554-3985-4738-9085-576c65391e44&response=json&sessionkey=NPIr%2Flm7%2Bu0dB9XxfOmuCTTHu%2B8%3D&_=1373617819883
> Attaching the MS logs.
--
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