[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-4486?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sudha Ponnaganti updated CLOUDSTACK-4486:
-----------------------------------------

    Priority: Critical  (was: Major)
    
> [Automation] Attach volume failed with NPE in KVM
> -------------------------------------------------
>
>                 Key: CLOUDSTACK-4486
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4486
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the 
> default.) 
>          Components: Automation, Volumes
>    Affects Versions: 4.2.0
>         Environment: KVM
> Automation
> Branch - 4.2-forward
>            Reporter: Rayees Namathponnan
>            Priority: Critical
>             Fix For: 4.2.1
>
>         Attachments: KVM_Regression_24_Aug_Agent.rar, 
> KVM_Regression_24_Aug_MS.rar
>
>
> This issue found during automation run
> test case 
> integration.component.test_volumes.TestAttachVolume.test_01_volume_attach 
> failed,
> Test case failed during attach volume; observed below NPE in MS
> 2013-08-23 20:28:40,676 DEBUG [agent.transport.Request] 
> (Job-Executor-162:job-572 = [ 50afeb63-5969-4291-a3c8-3f7092f641e1 ]) Seq 
> 1-105056046: Sending  { Cmd , MgmtId: 29066118877352, via: 1, Ver: v1, Flags: 
> 100011, 
> [{"org.apache.cloudstack.storage.command.CreateObjectCommand":{"data":{"org.apache.cloudstack.storage.to.VolumeObjectTO":{"uuid":"504963a2-e094-4513-9339-db2088196349","volumeType":"DATADISK","dataStore":{"org.apache.cloudstack.storage.to.PrimaryDataStoreTO":{"uuid":"fff90cb5-06dd-33b3-8815-d78c08ca01d9","id":1,"poolType":"NetworkFilesystem","host":"10.223.110.232","path":"/export/home/rayees/SC_QA_AUTO4/primary","port":2049}},"name":"TestDiskServ","size":1073741824,"volumeId":124,"accountId":79,"id":124,"hypervisorType":"KVM"}},"wait":0}}]
>  }
> 2013-08-23 20:28:40,755 DEBUG [agent.transport.Request] 
> (AgentManager-Handler-14:null) Seq 1-105056046: Processing:  { Ans: , MgmtId: 
> 29066118877352, via: 1, Ver: v1, Flags: 10, 
> [{"org.apache.cloudstack.storage.command.CreateObjectAnswer":{"result":false,"details":"java.lang.NullPointerException","wait":0}}]
>  }
> 2013-08-23 20:28:40,755 DEBUG [agent.transport.Request] 
> (Job-Executor-162:job-572 = [ 50afeb63-5969-4291-a3c8-3f7092f641e1 ]) Seq 
> 1-105056046: Received:  { Ans: , MgmtId: 29066118877352, via: 1, Ver: v1, 
> Flags: 10, { CreateObjectAnswer } }
> 2013-08-23 20:28:40,760 WARN  
> [storage.datastore.ObjectInDataStoreManagerImpl] (Job-Executor-162:job-572 = 
> [ 50afeb63-5969-4291-a3c8-3f7092f641e1 ]) Unsupported data object (VOLUME, 
> org.apache.cloudstack.storage.datastore.PrimaryDataStoreImpl@14441ccd), no 
> need to delete from object in store ref table
> 2013-08-23 20:28:40,761 DEBUG [cloud.storage.VolumeManagerImpl] 
> (Job-Executor-162:job-572 = [ 50afeb63-5969-4291-a3c8-3f7092f641e1 ]) create 
> volume failed: java.lang.NullPointerException
> 2013-08-23 20:28:40,783 ERROR [cloud.async.AsyncJobManagerImpl] 
> (Job-Executor-162:job-572 = [ 50afeb63-5969-4291-a3c8-3f7092f641e1 ]) 
> Unexpected exception while executing 
> org.apache.cloudstack.api.command.user.volume.AttachVolumeCmd
> com.cloud.utils.exception.CloudRuntimeException: create volume 
> failed:java.lang.NullPointerException
>         at 
> com.cloud.storage.VolumeManagerImpl.createVolume(VolumeManagerImpl.java:696)
>         at 
> com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
>         at 
> com.cloud.storage.VolumeManagerImpl.createVolumeOnPrimaryStorage(VolumeManagerImpl.java:1538)
>         at 
> com.cloud.storage.VolumeManagerImpl.attachVolumeToVM(VolumeManagerImpl.java:1862)
>         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)
> 2013-08-23 20:28:40,785 DEBUG [cloud.async.AsyncJobManagerImpl] 
> (Job-Executor-162:job-572 = [ 50afeb63-5969-4291-a3c8-3f7092f641e1 ]) 
> Complete async job-572 = [ 50afeb63-5969-4291-a3c8-3f7092f641e1 ], jobStatus: 
> 2, resultCode: 530, result: Error Code: 530 Error text: create volume 
> failed:java.lang.NullPointerException
> 2013-08-23 20:28:41,127 DEBUG 
> [network.router.VirtualNetworkApplianceManagerImpl] 
> (RouterStatusMonitor-1:null) Found 9 routers to update status. 
> 2013-08-23 20:28:41,128 DEBUG 
> [network.router.VirtualNetworkApplianceManagerImpl] 
> (RouterStatusMonitor-1:null) Found 1 networks to update RvR status. 
> 2013-08-23 20:28:41,138 DEBUG [agent.transport.Request] 
> (RedundantRouterStatusMonitor-1:null) Seq 1-105056047: Sending  { Cmd , 
> MgmtId: 29066118877352, via: 1, Ver: v1, Flags: 100011, 
> [{"com.cloud.agent.api.CheckRouterCommand":{"accessDetails":{"router.ip":"169.254.2.59","router.name":"r-86-QA"},"wait":30}}]
>  }
> 2013-08-23 20:28:41,248 DEBUG 
> [network.router.VirtualNetworkApplianceManagerImpl] 
> (RouterStatusMonitor-1:null) Found 9 routers to update status. 
> 2013-08-23 20:28:41,249 DEBUG 
> [network.router.VirtualNetworkApplianceManagerImpl] 
> (RouterStatusMonitor-1:null) Found 1 networks to update RvR status
> Attached MS and agent log

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

Reply via email to