Srikanteswararao Talluri created CLOUDSTACK-1880:
----------------------------------------------------

             Summary: Error while attaching a volume 
                 Key: CLOUDSTACK-1880
                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1880
             Project: CloudStack
          Issue Type: Bug
      Security Level: Public (Anyone can view this level - this is the default.)
          Components: Volumes
    Affects Versions: 4.2.0
            Reporter: Srikanteswararao Talluri
            Priority: Critical
             Fix For: 4.2.0


1. create a VM "VM1" with root volume on zone wide primary storage
2. create a volume "Vol1" on cluster wide primary storage, this should not be 
allowed as expected
3. create a VM "VM2" with root volume on cluster wide primary storage
4. try to attach "Vol1" to "VM2"

It is failing with following error: Can't move volume between scope: CLUSTER 
and ZONE


 ===START===  10.252.249.129 -- GET  
command=attachVolume&id=89927b7c-7849-496b-b8c8-161c59c630cc&virtualMachineId=dee911ab-bdf1-4497-a799-64b405f53b8b&response=json&sessionkey=FDm4fMQ93FjXjXmoBg%2FKrL6WrTU%3D&_=1364881487583
2013-04-02 16:40:52,408 DEBUG [cloud.async.AsyncJobManagerImpl] 
(catalina-exec-12:null) submit async job-103, details: AsyncJobVO {id:103, 
userId: 2, accountId: 2, sessionKey: null, instanceType: null, instanceId: 39, 
cmd: org.apache.cloudstack.api.command.user.volume.AttachVolumeCmd, 
cmdOriginator: null, cmdInfo: 
{"response":"json","id":"89927b7c-7849-496b-b8c8-161c59c630cc","sessionkey":"FDm4fMQ93FjXjXmoBg/KrL6WrTU\u003d","ctxUserId":"2","virtualMachineId":"dee911ab-bdf1-4497-a799-64b405f53b8b","_":"1364881487583","ctxAccountId":"2","ctxStartEventId":"365"},
 cmdVersion: 0, callbackType: 0, callbackAddress: null, status: 0, 
processStatus: 0, resultCode: 0, result: null, initMsid: 7566222426160, 
completeMsid: null, lastUpdated: null, lastPolled: null, created: null}
2013-04-02 16:40:52,411 DEBUG [cloud.api.ApiServlet] (catalina-exec-12:null) 
===END===  10.252.249.129 -- GET  
command=attachVolume&id=89927b7c-7849-496b-b8c8-161c59c630cc&virtualMachineId=dee911ab-bdf1-4497-a799-64b405f53b8b&response=json&sessionkey=FDm4fMQ93FjXjXmoBg%2FKrL6WrTU%3D&_=1364881487583
2013-04-02 16:40:52,414 DEBUG [cloud.async.AsyncJobManagerImpl] 
(Job-Executor-12:job-103) Executing 
org.apache.cloudstack.api.command.user.volume.AttachVolumeCmd for job-103
2013-04-02 16:40:52,494 ERROR [cloud.async.AsyncJobManagerImpl] 
(Job-Executor-12:job-103) 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 ZONE
        at 
com.cloud.storage.VolumeManagerImpl.needMoveVolume(VolumeManagerImpl.java:1512)
        at 
com.cloud.storage.VolumeManagerImpl.attachVolumeToVM(VolumeManagerImpl.java:1718)
        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:164)
        at 
com.cloud.async.AsyncJobManagerImpl$1.run(AsyncJobManagerImpl.java:437)
        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-04-02 16:40:52,495 DEBUG [cloud.async.AsyncJobManagerImpl] 
(Job-Executor-12:job-103) Complete async job-103, jobStatus: 2, resultCode: 
530, result: Error Code: 530 Error text: Can't move volume between scope: 
CLUSTER and ZONE


--
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

Reply via email to