cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rayees Namathponnan (JIRA)" <j...@apache.org>
Subject [jira] [Created] (CLOUDSTACK-4754) [Automation] Failed to create volume during vm deployment with null pointer exception in KVM
Date Fri, 27 Sep 2013 22:13:03 GMT
Rayees Namathponnan created CLOUDSTACK-4754:
-----------------------------------------------

             Summary: [Automation] Failed to create volume during vm deployment with null
pointer exception in KVM 
                 Key: CLOUDSTACK-4754
                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4754
             Project: CloudStack
          Issue Type: Bug
      Security Level: Public (Anyone can view this level - this is the default.)
          Components: API, Automation, KVM
    Affects Versions: 4.2.1
         Environment: KVM
branch - 4.2-forward branch

            Reporter: Rayees Namathponnan
            Priority: Blocker
             Fix For: 4.2.1


Few test cases from BVT suite failed during VM deployment;    below null pointer exception
observed 


2013-09-27 10:58:27,817 DEBUG [storage.volume.VolumeServiceImpl] (Job-Executor-102:job-219
= [ 13169ba1-00de-4cfc-84dd-2122324bb16f ]) 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:445)
        at org.apache.cloudstack.storage.volume.VolumeServiceImpl.createVolumeFromTemplateAsync(VolumeServiceImpl.java:574)
        at com.cloud.storage.VolumeManagerImpl.recreateVolume(VolumeManagerImpl.java:2547)
        at com.cloud.storage.VolumeManagerImpl.prepare(VolumeManagerImpl.java:2611)
        at com.cloud.vm.VirtualMachineManagerImpl.advanceStart(VirtualMachineManagerImpl.java:889)
        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:3404)
        at com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:2964)
        at com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:2950)
        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:679)
2013-09-27 10:58:27,843 INFO  [storage.volume.VolumeServiceImpl] (Job-Executor-102:job-219
= [ 13169ba1-00de-4cfc-84dd-2122324bb16f ]) releasing lock for VMTemplateStoragePool 6
2013-09-27 10:58:27,843 DEBUG [cloud.storage.VolumeManagerImpl] (Job-Executor-102:job-219
= [ 13169ba1-00de-4cfc-84dd-2122324bb16f ]) Unable to create Vol[58|vm=52|ROOT]:java.lan
g.NullPointerException
2013-09-27 10:58:27,843 INFO  [cloud.vm.VirtualMachineManagerImpl] (Job-Executor-102:job-219
= [ 13169ba1-00de-4cfc-84dd-2122324bb16f ]) Unable to contact resource.
com.cloud.exception.StorageUnavailableException: Resource [StoragePool:1] is unreachable:
Unable to create Vol[58|vm=52|ROOT]:java.lang.NullPointerException
        at com.cloud.storage.VolumeManagerImpl.recreateVolume(VolumeManagerImpl.java:2560)
        at com.cloud.storage.VolumeManagerImpl.prepare(VolumeManagerImpl.java:2611)
        at com.cloud.vm.VirtualMachineManagerImpl.advanceStart(VirtualMachineManagerImpl.java:889)
        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:3404)
        at com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:2964)
        at com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:2950)
        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:679)
2013-09-27 10:58:27,849 DEBUG [cloud.vm.VirtualMachineManagerImpl] (Job-Executor-102:job-219
= [ 13169ba1-00de-4cfc-84dd-2122324bb16f ]) Cleaning up resources for the vm VM[User|9db3aac9-9daf-4da8-8d6f-ec1c6ec21240]
in Starting state


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