You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cloudstack.apache.org by "Srikanteswararao Talluri (JIRA)" <ji...@apache.org> on 2013/06/12 13:02:20 UTC
[jira] [Created] (CLOUDSTACK-2958) [ZWPS][VMWARE]: NPE while
attaching a volume to a VM
Srikanteswararao Talluri created CLOUDSTACK-2958:
----------------------------------------------------
Summary: [ZWPS][VMWARE]: NPE while attaching a volume to a VM
Key: CLOUDSTACK-2958
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2958
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: Blocker
Fix For: 4.2.0
1. Deploy a vmware zone with zone wide primary storage
2. create an Instance
3. Take snaphot of the root volume
4. create volume from snapshot
5. attach the volume created in step 4 to the vm created in step 2.
NOTE: Zone has multiple zone wide primary storages
===START=== 10.252.192.7 -- GET command=attachVolume&id=214ee1ea-1b05-4e05-b967-8db48b318dca&virtualMachineId=7092ef40-8aef-40fa-a3a0-8ae2443109a7&response=json&sessionkey=5ez1jBXiPUJzcam0%2Ft9UtTy9L%2BY%3D&_=1371034570223
2013-06-12 21:51:37,493 DEBUG [cloud.async.AsyncJobManagerImpl] (catalina-exec-11:null) submit async job-20, details: AsyncJobVO {id:20, userId: 2, accountId: 2, sessionKey: null, instanceType: Volume, instanceId: 7, cmd: org.apache.cloudstack.api.command.user.volume.AttachVolumeCmd, cmdOriginator: null, cmdInfo: {"response":"json","id":"214ee1ea-1b05-4e05-b967-8db48b318dca","sessionkey":"5ez1jBXiPUJzcam0/t9UtTy9L+Y\u003d","ctxUserId":"2","virtualMachineId":"7092ef40-8aef-40fa-a3a0-8ae2443109a7","httpmethod":"GET","_":"1371034570223","ctxAccountId":"2","ctxStartEventId":"78"}, 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-06-12 21:51:37,497 DEBUG [cloud.api.ApiServlet] (catalina-exec-11:null) ===END=== 10.252.192.7 -- GET command=attachVolume&id=214ee1ea-1b05-4e05-b967-8db48b318dca&virtualMachineId=7092ef40-8aef-40fa-a3a0-8ae2443109a7&response=json&sessionkey=5ez1jBXiPUJzcam0%2Ft9UtTy9L%2BY%3D&_=1371034570223
2013-06-12 21:51:37,500 DEBUG [cloud.async.AsyncJobManagerImpl] (Job-Executor-8:job-20) Executing org.apache.cloudstack.api.command.user.volume.AttachVolumeCmd for job-20
2013-06-12 21:51:37,610 ERROR [cloud.async.AsyncJobManagerImpl] (Job-Executor-8:job-20) Unexpected exception while executing org.apache.cloudstack.api.command.user.volume.AttachVolumeCmd
java.lang.NullPointerException
at com.cloud.storage.VolumeManagerImpl.needMoveVolume(VolumeManagerImpl.java:1502)
at com.cloud.storage.VolumeManagerImpl.attachVolumeToVM(VolumeManagerImpl.java:1741)
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: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-06-12 21:51:37,612 DEBUG [cloud.async.AsyncJobManagerImpl] (Job-Executor-8:job-20) Complete async job-20, jobStatus: 2, resultCode: 530, result: Error Code: 530 Error text: null
2013-06-12 21:51:39,145 DEBUG [network.router.VirtualNetworkApplianceManagerImpl] (RouterStatusMonitor-1:null) Found 1 routers to update status.
--
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