[ https://issues.apache.org/jira/browse/CLOUDSTACK-4588?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Rayees Namathponnan updated CLOUDSTACK-4588: -------------------------------------------- Attachment: CLOUDSTACK-4588.rar > [Automation][Vmware] VM deployment failed while creating Volume with NPE > ------------------------------------------------------------------------ > > Key: CLOUDSTACK-4588 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4588 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: VMware > Affects Versions: 4.2.0 > Environment: Vmware > Reporter: Rayees Namathponnan > Priority: Critical > Fix For: 4.2.1 > > Attachments: CLOUDSTACK-4588.rar > > > Issue observed during automation; two suites failed while deploying vm with > default template > test case failed while creating volume, observed below NPE > 62be7-c154-35de-a3ad-01a5a14e382a in storage pool 1 with > VMTemplateStoragePool id: 7 > 2013-09-01 11:58:16,953 DEBUG [storage.volume.VolumeServiceImpl] > (Job-Executor-78:job-189 = [ 373776bc-bd4e-4d3c-b785-9418fe477ed5 ]) Acquire > lock on VMTemplateStoragePool 7 with timeout 3600 seconds > 2013-09-01 11:58:16,955 INFO [storage.volume.VolumeServiceImpl] > (Job-Executor-78:job-189 = [ 373776bc-bd4e-4d3c-b785-9418fe477ed5 ]) lock is > acquired for VMTemplateStoragePool 7 > 2013-09-01 11:58:16,959 DEBUG [storage.volume.VolumeServiceImpl] > (Job-Executor-78:job-189 = [ 373776bc-bd4e-4d3c-b785-9418fe477ed5 ]) failed > to create template on storage > java.lang.NullPointerException > at > org.apache.cloudstack.storage.motion.DataMotionServiceImpl.copyAsync(DataMotionServiceImpl.java:45) > at > org.apache.cloudstack.storage.volume.VolumeServiceImpl.createBaseImageAsync(VolumeServiceImpl.java:440) > at > org.apache.cloudstack.storage.volume.VolumeServiceImpl.createVolumeFromTemplateAsync(VolumeServiceImpl.java:569) > at > com.cloud.storage.VolumeManagerImpl.recreateVolume(VolumeManagerImpl.java:2536) > at > com.cloud.storage.VolumeManagerImpl.prepare(VolumeManagerImpl.java:2592) > at > com.cloud.vm.VirtualMachineManagerImpl.advanceStart(VirtualMachineManagerImpl.java:888) > at > com.cloud.vm.VirtualMachineManagerImpl.start(VirtualMachineManagerImpl.java:578) > at > org.apache.cloudstack.engine.cloud.entity.api.VMEntityManagerImpl.deployVirtualMachine(VMEntityManagerImpl.java:227) > at > org.apache.cloudstack.engine.cloud.entity.api.VirtualMachineEntityImpl.deploy(VirtualMachineEntityImpl.java:209) > at > com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:3406) > at > com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:2966) > at > com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:2952) > at > com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125) > at > org.apache.cloudstack.api.command.user.vm.DeployVMCmd.execute(DeployVMCmd.java:420) > 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) > 2013-09-01 11:58:16,981 INFO [storage.volume.VolumeServiceImpl] > (Job-Executor-78:job-189 = [ 373776bc-bd4e-4d3c-b785-9418fe477ed5 ]) > releasing lock for VMTemplateStoragePool 7 > 2013-09-01 11:58:16,982 DEBUG [cloud.storage.VolumeManagerImpl] > (Job-Executor-78:job-189 = [ 373776bc-bd4e-4d3c-b785-9418fe477ed5 ]) Unable > to create Vol[58|vm=55|ROOT]:java.lang.NullPointerException -- 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