[ https://issues.apache.org/jira/browse/CLOUDSTACK-3227?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13696938#comment-13696938 ]
Koushik Das commented on CLOUDSTACK-3227: ----------------------------------------- The one related to snapshot created volume is already addressed as part of CLOUDSTACK-2276. And the other one is tracked by CLOUDSTACK-3107. So resolving as duplicate again. > Attach volume fails in case of uploaded volume and volume created from > snapshot > ------------------------------------------------------------------------------- > > Key: CLOUDSTACK-3227 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3227 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Snapshot > Affects Versions: 4.2.0 > Environment: build: > CloudPlatform-4.2-117-rhel6.3 > Reporter: shweta agarwal > Assignee: Koushik Das > Priority: Blocker > Fix For: 4.2.0 > > > Repro steps: > 1. Create a VM > 2. Upload a volume compatible to VM created > 3. Attach volume to VM > 4. Create volume from a snapshot > 5. Attach the volume created from snapshot > Bug: > attach volume will fail in both step 3 and 4 > Expected Result: > attach volume should pass in all types of volume > MS log shows: > in case we try to attach snapshot created volume > 2013-06-27 14:00:03,226 ERROR [cloud.async.AsyncJobManagerImpl] > (Job-Executor-6:job-323) Unexpected exception while executing > org.apache.cloudstack.api.command.user.volume.AttachVolumeCmd > java.lang.NullPointerException > at > com.cloud.storage.VolumeManagerImpl.copyVolume(VolumeManagerImpl.java:1443) > at > com.cloud.storage.VolumeManagerImpl.createVolumeOnPrimaryStorage(VolumeManagerImpl.java:1487) > at > com.cloud.storage.VolumeManagerImpl.attachVolumeToVM(VolumeManagerImpl.java:1733) > 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:1146) > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) > at java.lang.Thread.run(Thread.java:679) > 2013-06-27 14:00:03, > in case we try to attach uploaded volume: > Unexpected exception while executing > org.apache.cloudstack.api.command.user.volume.AttachVolumeCmd > java.lang.NullPointerException > at > com.cloud.storage.VolumeManagerImpl.needMoveVolume(VolumeManagerImpl.java:1503) > at > com.cloud.storage.VolumeManagerImpl.attachVolumeToVM(VolumeManagerImpl.java:1742) > 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:1146) > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) > at java.lang.Thread.run(Thread.java:679) > Seems attach volumes fails every time it need to copy volume from secondary > to primary . -- 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