Rayees Namathponnan created CLOUDSTACK-3599:
-----------------------------------------------
Summary: [Automation] [BVT] Attach volume failed with null pointer
exception
Key: CLOUDSTACK-3599
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3599
Project: CloudStack
Issue Type: Bug
Security Level: Public (Anyone can view this level - this is the default.)
Components: Volumes
Affects Versions: 4.2.0
Environment: Vmware
4.2 branch
Reporter: Rayees Namathponnan
Fix For: 4.2.0
Volume test cases from BVT suite failed in VMware
integration.smoke.test_volumes.TestCreateVolume.test_01_create_volume
Observer below NPE while calling API createVolumeCallback
ERROR [cloud.async.AsyncJobManagerImpl] (Job-Executor-70:job-62 = [
28d50ad1-0d29-4679-9095-a3e0ac997e9a ]) Unexpected exception while executing
org.apache.cloudstack.api.command.user.volume.AttachVolumeCmd
java.lang.RuntimeException: InvocationTargetException when invoking RPC
callback for command: createVolumeCallback
at
org.apache.cloudstack.framework.async.AsyncCallbackDispatcher.dispatch(AsyncCallbackDispatcher.java:148)
at
org.apache.cloudstack.framework.async.InplaceAsyncCallbackDriver.performCompletionCallback(InplaceAsyncCallbackDriver.java:26)
at
org.apache.cloudstack.framework.async.AsyncCallbackDispatcher.complete(AsyncCallbackDispatcher.java:120)
at
org.apache.cloudstack.storage.datastore.driver.CloudStackPrimaryDataStoreDriverImpl.createAsync(CloudStackPrimaryDataStoreDriverImpl.java:122)
at
org.apache.cloudstack.storage.volume.VolumeServiceImpl.createVolumeAsync(VolumeServiceImpl.java:170)
at
com.cloud.storage.VolumeManagerImpl.createVolume(VolumeManagerImpl.java:703)
at
com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
at
com.cloud.storage.VolumeManagerImpl.createVolumeOnPrimaryStorage(VolumeManagerImpl.java:1542)
at
com.cloud.storage.VolumeManagerImpl.attachVolumeToVM(VolumeManagerImpl.java:1828)
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:722)
Caused by: java.lang.reflect.InvocationTargetException
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:601)
at
org.apache.cloudstack.framework.async.AsyncCallbackDispatcher.dispatch(AsyncCallbackDispatcher.java:142)
... 26 more
Caused by: java.lang.NullPointerException
at
org.apache.cloudstack.storage.volume.VolumeObject.processEvent(VolumeObject.java:482)
at
org.apache.cloudstack.storage.volume.VolumeServiceImpl.createVolumeCallback(VolumeServiceImpl.java:180)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
... 30 more
INFO [vmware.mo.HypervisorHostHelper] (DirectAgent-289:10.223.250.131) Blank
VM: i-11-14-VM is ready for use
INFO [vmware.resource.VmwareResource] (DirectAgent-289:10.223.250.131) Prepare
NIC device based on NicTO:
{"deviceId":0,"networkRateMbps":200,"defaultNic":true,"uuid":"b7f53ef0-196b-4647-8327-4bc53c46b18a","ip":"10.1.1.50","netmask":"255.255.255.0","gateway":"10.1.1.1","mac":"02:00:36:ef:00:01","dns1":"8.8.8.8","broadcastType":"Vlan","type":"Guest","broadcastUri":"vlan://3196","isolationUri":"vlan://3196","isSecurityGroupEnabled":false}
--
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
