You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cloudstack.apache.org by "Koushik Das (JIRA)" <ji...@apache.org> on 2013/05/30 15:19:20 UTC
[jira] [Resolved] (CLOUDSTACK-2619) Volume created from Snapshot
does not attach to the VM.fails with NPE.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2619?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Koushik Das resolved CLOUDSTACK-2619.
-------------------------------------
Resolution: Duplicate
> Volume created from Snapshot does not attach to the VM.fails with NPE.
> ----------------------------------------------------------------------
>
> Key: CLOUDSTACK-2619
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2619
> 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: Kiran Koneti
> Assignee: Koushik Das
> Priority: Blocker
> Fix For: 4.2.0
>
> Attachments: management-server.zip
>
>
> 1)Create a VMware Advanced Zone setup.
> 2)Once the Builtin template is downloaded then created a Vm and took snapshot for the same.
> 3)Created a volume from the snapshot created in the step 2.
> 4) I see the volume creation was successful in the UI.
> 5)Tried to check the volume details but couldn't find it either in primary nor in secondary storage.
> 6)Observed the Volumes details in the DB and it shows state as allocated and the Location as Null.
> "*************************** 6. row ***************************
> id: 6
> account_id: 2
> domain_id: 1
> pool_id: NULL
> last_pool_id: NULL
> instance_id: NULL
> device_id: NULL
> name: CreatedVolume
> uuid: 858d9047-899b-4d2a-95fe-d1ac33154aa8
> size: 2147483648
> folder: NULL
> path: c394b91e99774acd8bbbbe9c30f890d3
> pod_id: NULL
> data_center_id: 1
> iscsi_name: NULL
> host_ip: NULL
> volume_type: DATADISK
> pool_type: NULL
> disk_offering_id: 2
> template_id: 7
> first_snapshot_backup_uuid: NULL
> recreatable: 0
> created: 2013-05-22 14:18:28
> attached: NULL
> updated: 2013-05-22 14:18:28
> removed: NULL
> state: Allocated
> chain_info: NULL
> update_count: 0
> disk_type: NULL
> display_volume: 1
> 6 rows in set (0.00 sec)"
> Then I tried to attach this volume to a VM and it fails with an NPE as mentioned below
> "2013-05-22 20:16:02,983 DEBUG [agent.transport.Request] (DirectAgent-202:null) Seq 1-1002242356: Processing: { Ans: , MgmtId: 6703101771911, via: 1, Ver: v1, Flags: 110, [{"storage.CreateAnswer":{"volume":{"id":6,"name":"CreatedVolume","mountPoint":"/export/home/kiran/p1","path":"a300f5598c63435c948deb4cc313a4b7","size":2147483648,"type":"DATADISK","storagePoolType":"NetworkFilesystem","storagePoolUuid":"b4825bd6-2b6d-33ef-b324-bfbbec982716","deviceId":0},"requestTemplateReload":false,"result":true,"wait":0}}] }
> 2013-05-22 20:16:02,985 DEBUG [agent.transport.Request] (Job-Executor-17:job-17) Seq 1-1002242356: Received: { Ans: , MgmtId: 6703101771911, via: 1, Ver: v1, Flags: 110, { CreateAnswer } }
> 2013-05-22 20:16:02,990 DEBUG [agent.manager.AgentAttache] (DirectAgent-202:null) Seq 1-1002242356: No more commands found
> 2013-05-22 20:16:03,062 ERROR [cloud.async.AsyncJobManagerImpl] (Job-Executor-17:job-17) Unexpected exception while executing org.apache.cloudstack.api.command.user.volume.AttachVolumeCmd
> java.lang.NullPointerException
> at com.cloud.storage.VolumeManagerImpl.needMoveVolume(VolumeManagerImpl.java:1500)
> at com.cloud.storage.VolumeManagerImpl.attachVolumeToVM(VolumeManagerImpl.java:1730)
> 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-05-22 20:16:03,065 DEBUG [cloud.async.AsyncJobManagerImpl] (Job-Executor-17:job-17) Complete async job-17, jobStatus: 2, resultCode: 530, result: Error Code: 530 Error text: null"
> Attaching the management server 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