You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cloudstack.apache.org by "Likitha Shetty (JIRA)" <ji...@apache.org> on 2013/07/22 17:32:49 UTC

[jira] [Comment Edited] (CLOUDSTACK-3107) NPE while attaching the volume which is added thru uploadVolume

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

Likitha Shetty edited comment on CLOUDSTACK-3107 at 7/22/13 3:32 PM:
---------------------------------------------------------------------

The NPE mentioned in this bug has been fixed in 4.2

With the fix in place,
Xenserver
--------------
Attaching a volume to a VM that has been added through uploadVolume will succeed.

Vmware
------------
Attaching a volume to a VM that has been added through uploadVolume will fail with the following NPE

2013-07-22 11:13:31,174 ERROR [cloud.async.AsyncJobManagerImpl] (Job-Executor-45:job-87 = [ a42e7920-8584-4734-8c39-66f134ed8c01 ]) Unexpected exception while executing org.apache.cloudstack.api.command.user.volume.AttachVolumeCmd
java.lang.NullPointerException
        at com.cloud.storage.VolumeManagerImpl.needMoveVolume(VolumeManagerImpl.java:1567)
        at com.cloud.storage.VolumeManagerImpl.attachVolumeToVM(VolumeManagerImpl.java:1837)
        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:158)
        at com.cloud.async.AsyncJobManagerImpl$1.run(AsyncJobManagerImpl.java:531)
        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)

This NPE is caused by,
2013-07-22 11:13:31,174 DEBUG [storage.motion.AncientDataMotionStrategy] (Job-Executor-42:job-115 = [ 0d97cf94-37d4-41fd-8640-2a490aff6bc9 ]) copy to image store failed: java.lang.NullPointerException
		at com.cloud.storage.resource.VmwareSecondaryStorageResourceHandler.executeRequest(VmwareSecondaryStorageResourceHandler.java:105)
		at com.cloud.storage.resource.PremiumSecondaryStorageResource.executeRequest(PremiumSecondaryStorageResource.java:56)
		at com.cloud.agent.Agent.processRequest(Agent.java:525)
		at com.cloud.agent.Agent$AgentRequestHandler.doTask(Agent.java:852)
		at com.cloud.utils.nio.Task.run(Task.java:83)
		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)

The above NPE is also the root cause of issue - https://issues.apache.org/jira/browse/CLOUDSTACK-3629.   
                
      was (Author: likithas):
    The NPE mentioned in this bug has been fixed in 4.2

Xenserver
--------------
Attaching a volume to a VM that has been added through uploadVolume will succeed.

Vmware
------------
Attaching a volume to a VM that has been added through uploadVolume will fail with the following NPE

2013-07-22 11:13:31,174 ERROR [cloud.async.AsyncJobManagerImpl] (Job-Executor-45:job-87 = [ a42e7920-8584-4734-8c39-66f134ed8c01 ]) Unexpected exception while executing org.apache.cloudstack.api.command.user.volume.AttachVolumeCmd
java.lang.NullPointerException
        at com.cloud.storage.VolumeManagerImpl.needMoveVolume(VolumeManagerImpl.java:1567)
        at com.cloud.storage.VolumeManagerImpl.attachVolumeToVM(VolumeManagerImpl.java:1837)
        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:158)
        at com.cloud.async.AsyncJobManagerImpl$1.run(AsyncJobManagerImpl.java:531)
        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)

This NPE is caused by,
2013-07-22 11:13:31,174 DEBUG [storage.motion.AncientDataMotionStrategy] (Job-Executor-42:job-115 = [ 0d97cf94-37d4-41fd-8640-2a490aff6bc9 ]) copy to image store failed: java.lang.NullPointerException
		at com.cloud.storage.resource.VmwareSecondaryStorageResourceHandler.executeRequest(VmwareSecondaryStorageResourceHandler.java:105)
		at com.cloud.storage.resource.PremiumSecondaryStorageResource.executeRequest(PremiumSecondaryStorageResource.java:56)
		at com.cloud.agent.Agent.processRequest(Agent.java:525)
		at com.cloud.agent.Agent$AgentRequestHandler.doTask(Agent.java:852)
		at com.cloud.utils.nio.Task.run(Task.java:83)
		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)

The above NPE is also the root cause of issue - https://issues.apache.org/jira/browse/CLOUDSTACK-3629.   
                  
> NPE while attaching the volume which is added thru uploadVolume 
> ----------------------------------------------------------------
>
>                 Key: CLOUDSTACK-3107
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3107
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: Storage Controller
>    Affects Versions: 4.2.0
>         Environment: MS :  RHEL 6.3 
>            Reporter: Sailaja Mada
>            Assignee: Likitha Shetty
>            Priority: Critical
>             Fix For: 4.2.0
>
>         Attachments: apilog.log, management-server.log
>
>
> Steps:
> 1. Configured Advanced Zone with VMWARE 
> 2. Added new volume with .ova format using upload volume
> 3. When the volume got in to uploaded state , tried to add to the instance
> Observation:  It failed with NPE. (Attached the log)
> 2013-06-21 11:20:42,793 DEBUG [cloud.async.AsyncJobManagerImpl] (catalina-exec-1:null) submit async job-76, details: AsyncJobVO {id:76, userId: 3, accountId: 3, sessionKey: null, instanceType: Volume, instanceId: 18, cmd: org.apache.cloudstack.api.command.user.volume.AttachVolumeCmd, cmdOriginator: null, cmdInfo: {"response":"json","id":"df818343-2c19-4129-9ca7-ebe886a1063c","sessionkey":"RNaZZnzH0NfhX0IJaRwpz7wq9sY\u003d","ctxUserId":"3","virtualMachineId":"54536078-e4c5-4ad0-a87e-2817061264f0","httpmethod":"GET","_":"1371794030143","ctxAccountId":"3","ctxStartEventId":"326"}, cmdVersion: 0, callbackType: 0, callbackAddress: null, status: 0, processStatus: 0, resultCode: 0, result: null, initMsid: 94838926819810, completeMsid: null, lastUpdated: null, lastPolled: null, created: null}
> 2013-06-21 11:20:42,796 DEBUG [cloud.api.ApiServlet] (catalina-exec-1:null) ===END===  10.144.6.19 -- GET  command=attachVolume&id=df818343-2c19-4129-9ca7-ebe886a1063c&virtualMachineId=54536078-e4c5-4ad0-a87e-2817061264f0&response=json&sessionkey=RNaZZnzH0NfhX0IJaRwpz7wq9sY%3D&_=1371794030143
> 2013-06-21 11:20:42,826 DEBUG [cloud.async.AsyncJobManagerImpl] (Job-Executor-102:job-76) Executing org.apache.cloudstack.api.command.user.volume.AttachVolumeCmd for job-76
> 2013-06-21 11:20:42,938 DEBUG [cloud.user.AccountManagerImpl] (Job-Executor-102:job-76) Access to org.apache.cloudstack.storage.volume.VolumeObject@6876d38e granted to Acct[3-user1] by DomainChecker_EnhancerByCloudStack_97621a92
> 2013-06-21 11:20:42,939 DEBUG [cloud.user.AccountManagerImpl] (Job-Executor-102:job-76) Access to VM[User|useri2] granted to Acct[3-user1] by DomainChecker_EnhancerByCloudStack_97621a92
> 2013-06-21 11:20:42,966 ERROR [cloud.async.AsyncJobManagerImpl] (Job-Executor-102:job-76) 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:1110)
>         at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
>         at java.lang.Thread.run(Thread.java:679)
> 2013-06-21 11:20:42,984 DEBUG [cloud.async.AsyncJobManagerImpl] (Job-Executor-102:job-76) Complete async job-76, jobStatus: 2, resultCode: 530, result: Error Code: 530 Error text: null
> 2013-06-21 11:20:44,071 DEBUG [agent.manager.DirectAgentAttache] (DirectAgent-199:null) Ping from 1

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