cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "prashant kumar mishra (JIRA)" <j...@apache.org>
Subject [jira] [Created] (CLOUDSTACK-3491) delete host resulting NPE; Exception caught while handling disconnect: java.lang.NullPointerException
Date Fri, 12 Jul 2013 07:43:48 GMT
prashant kumar mishra created CLOUDSTACK-3491:
-------------------------------------------------

             Summary: delete host resulting NPE; Exception caught while handling disconnect:
java.lang.NullPointerException
                 Key: CLOUDSTACK-3491
                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3491
             Project: CloudStack
          Issue Type: Bug
      Security Level: Public (Anyone can view this level - this is the default.)
          Components: Management Server
    Affects Versions: 4.2.0
         Environment: vmware esxi 5.1
            Reporter: prashant kumar mishra
            Priority: Minor
             Fix For: 4.2.0


Steps to reproduce
---------------------------
1-prapare a CS setup with vmware esxi5.1
2-put host in maintenance mode
3-Remove host from CS

Expected
--------------
Host should get remove without any exception 

Actual
----------
remove host was successful  with NPE

Logs
--------
2013-07-12 08:58:04,530 ERROR [agent.manager.AgentManagerImpl] (AgentTaskPool-4:null) Exception
caught while handling disconnect:
java.lang.NullPointerException
        at com.cloud.host.dao.HostDaoImpl.updateState(HostDaoImpl.java:805)
        at com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
        at com.cloud.host.dao.HostDaoImpl.updateState(HostDaoImpl.java:68)
        at com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
        at com.cloud.utils.fsm.StateMachine2.transitTo(StateMachine2.java:111)
        at com.cloud.agent.manager.AgentManagerImpl.agentStatusTransitTo(AgentManagerImpl.java:1435)
        at com.cloud.agent.manager.AgentManagerImpl.disconnectAgent(AgentManagerImpl.java:1454)
        at com.cloud.agent.manager.AgentManagerImpl.handleDisconnectWithoutInvestigation(AgentManagerImpl.java:885)
        at com.cloud.agent.manager.ClusteredAgentManagerImpl.handleDisconnect(ClusteredAgentManagerImpl.java:291)
        at com.cloud.agent.manager.ClusteredAgentManagerImpl.handleDisconnectWithoutInvestigation(ClusteredAgentManagerImpl.java:280)
        at com.cloud.agent.manager.AgentManagerImpl$DisconnectTask.run(AgentManagerImpl.java:986)
        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-12 08:58:05,541 DEBUG [agent.manager.AgentManagerImpl] (AgentManager-Handler-1:null)
SeqA 7-9828: Processing Seq 7-9828:  { Cmd , MgmtId: -1, via: 7, Ver: v1, Flags: 11, [{"ConsoleProxyLoadReportCommand":{"_proxyVmId":41,"_loadInfo":"{\n
 \"connections\": []\n}","wait":0}}] }





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