Rayees Namathponnan created CLOUDSTACK-4025:
-----------------------------------------------

             Summary: [Automation] NullPointer Exception observed while 
destroying the VM during starting state
                 Key: CLOUDSTACK-4025
                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4025
             Project: CloudStack
          Issue Type: Bug
      Security Level: Public (Anyone can view this level - this is the default.)
          Components: API, Management Server
    Affects Versions: 4.2.0
         Environment: 4.2 build
KVM 
            Reporter: Rayees Namathponnan
            Priority: Critical
             Fix For: 4.2.0


Below null pointer observed in MS log during regression automation run,  i dont 
know which test case cause this; from the log, looks like its happening 
destroying account while vm is in  that account is in start state 


2013-07-05 10:03:07,296 DEBUG [cloud.network.NetworkManagerImpl] 
(Job-Executor-150:job-3471 = [ b7a4bcd9-aaa9-44fd-8256-d7fb4cf57c13 ]) Lock is 
released for network id 755 as
a part of network implement
2013-07-05 10:03:07,296 ERROR [cloud.vm.VirtualMachineManagerImpl] 
(Job-Executor-150:job-3471 = [ b7a4bcd9-aaa9-44fd-8256-d7fb4cf57c13 ]) Failed 
to start instance VM[User|3384
7e84-b811-4132-aa30-12b65385d397]
java.lang.NullPointerException
        at 
com.cloud.network.NetworkManagerImpl.prepare(NetworkManagerImpl.java:2081)
        at 
com.cloud.vm.VirtualMachineManagerImpl.advanceStart(VirtualMachineManagerImpl.java:932)
        at 
com.cloud.vm.VirtualMachineManagerImpl.start(VirtualMachineManagerImpl.java:624)
        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:3408)
        at 
com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:1954)
        at 
com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
        at 
org.apache.cloudstack.api.command.user.vm.StartVMCmd.execute(StartVMCmd.java:120)
        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-07-05 10:03:07,299 DEBUG [cloud.vm.VirtualMachineManagerImpl] 
(Job-Executor-150:job-3471 = [ b7a4bcd9-aaa9-44fd-8256-d7fb4cf57c13 ]) Cleaning 
up resources for the vm VM[User|33847e84-b811-4132-aa30-12b65385d397] in 
Starting state
2013-07-05 10:03:07,300 DEBUG [agent.transport.Request] 
(Job-Executor-150:job-3471 = [ b7a4bcd9-aaa9-44fd-8256-d7fb4cf57c13 ]) Seq 
4-1845366559: Sending  { Cmd , MgmtId: 29066118877352, via: 4, Ver: v1, Flags: 
100011, 
[{"com.cloud.agent.api.StopCommand":{"isProxy":false,"executeInSequence":false,"vmName":"i-735-1074-QA","wait":0}}]
 }
2013-07-05 10:03:07,534 DEBUG [agent.transport.Request] 
(AgentManager-Handler-8:null) Seq 4-1845366559: Processing:  { Ans: , MgmtId: 
29066118877352, via: 4, Ver: v1, Flags: 10, 
[{"com.cloud.agent.api.StopAnswer":{"vncPort":0,"result":true,"wait":0}}] }
2013-07-05 10:03:07,535 DEBUG [agent.transport.Request] 
(Job-Executor-150:job-3471 = [ b7a4bcd9-aaa9-44fd-8256-d7fb4cf57c13 ]) Seq 
4-1845366559: Received:  { Ans: , MgmtId: 29066118877352, via: 4, Ver: v1, 
Flags: 10, { StopAnswer } }





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