cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rajesh Battala (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CLOUDSTACK-2420) NPE: Attaching an Uploaded volume to a VM, (NPE while moving from
Date Thu, 09 May 2013 13:13:16 GMT

    [ https://issues.apache.org/jira/browse/CLOUDSTACK-2420?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13652945#comment-13652945
] 

Rajesh Battala commented on CLOUDSTACK-2420:
--------------------------------------------

DB entry of the volume :
                        id: 10
                account_id: 2
                 domain_id: 1
                   pool_id: NULL
              last_pool_id: NULL
               instance_id: NULL
                 device_id: NULL
                      name: TestVol1
                      uuid: e0075fb1-2432-4375-a22e-b7e6015afac6
                      size: 0
                    folder: NULL
                      path: NULL
                    pod_id: NULL
            data_center_id: 1
                iscsi_name: NULL
                   host_ip: NULL
               volume_type: DATADISK
                 pool_type: NULL
          disk_offering_id: 6
               template_id: NULL
first_snapshot_backup_uuid: NULL
               recreatable: 0
                   created: 2013-05-09 12:58:44
                  attached: NULL
                   updated: 2013-05-09 12:58:44
                   removed: NULL
                     state: Uploaded
                chain_info: NULL
              update_count: 2
                 disk_type: NULL
                
> NPE: Attaching an Uploaded volume to a VM, (NPE while moving from 
> ------------------------------------------------------------------
>
>                 Key: CLOUDSTACK-2420
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2420
>             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: Rajesh Battala
>             Fix For: 4.2.0
>
>
> 2013-05-09 18:36:46,997 DEBUG [cloud.api.ApiServlet] (6876027@qtp-10225875-14:null) ===END===
 10.144.7.13 -- GET  command=attachVolume&id=e0075fb1-2432-4375-a22e-b7e6015afac6&virtualMachineId=aa6b941d-a7ea-42da-a175-578005fcb41b&response=json&sessionkey=vCZWZNneQ9l2xOkDXYUoEuAluYw%3D&_=1368104845639
> 2013-05-09 18:36:47,077 ERROR [cloud.async.AsyncJobManagerImpl] (Job-Executor-6:job-29)
Unexpected exception while executing org.apache.cloudstack.api.command.user.volume.AttachVolumeCmd
> java.lang.NullPointerException
>         at com.cloud.storage.VolumeManagerImpl.copyVolume(VolumeManagerImpl.java:1444)
>         at com.cloud.storage.VolumeManagerImpl.createVolumeOnPrimaryStorage(VolumeManagerImpl.java:1488)
>         at com.cloud.storage.VolumeManagerImpl.attachVolumeToVM(VolumeManagerImpl.java:1727)
>         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:722)
> 2013-05-09 18:36:47,080 DEBUG [cloud.async.AsyncJobManagerImpl] (Job-Executor-6:job-29)
Complete async job-29, jobStatus: 2, resultCode: 530, result: Error Code: 530 Error text:
null

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

Mime
View raw message