You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cloudstack.apache.org by "venkata swamybabu budumuru (JIRA)" <ji...@apache.org> on 2013/07/23 11:45:11 UTC
[jira] [Reopened] (CLOUDSTACK-2418) [GSLB] NPE while removing the
GSLB enabled Netscaler device
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2418?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
venkata swamybabu budumuru reopened CLOUDSTACK-2418:
----------------------------------------------------
Still seeing the same issue mentioned in the bug while deleting the NS that is enabled for GSLB. Delete goes fine but, it throws NPE as mentioned below.
07-23 15:13:13,271 DEBUG [cloud.async.AsyncJobManagerImpl] (Job-Executor-65:job-163 = [ 80888577-be56-4840-95d7-c9fe2156f3a8 ]) Complete async job-163 = [ 80888577-be56-4840-95d7-c9fe2156f3a8 ], jobStatus: 1, resultCode: 0, result: org.apache.cloudstack.api.respons
e.SuccessResponse@4700a893
2013-07-23 15:13:13,277 ERROR [agent.manager.AgentManagerImpl] (AgentTaskPool-9:null) Exception caught while handling disconnect:
java.lang.NullPointerException
at com.cloud.host.dao.HostDaoImpl.updateState(HostDaoImpl.java:876)
at com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
at com.cloud.host.dao.HostDaoImpl.updateState(HostDaoImpl.java:69)
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:1407)
at com.cloud.agent.manager.AgentManagerImpl.disconnectAgent(AgentManagerImpl.java:1426)
at com.cloud.agent.manager.AgentManagerImpl.handleDisconnectWithoutInvestigation(AgentManagerImpl.java:857)
at com.cloud.agent.manager.ClusteredAgentManagerImpl.handleDisconnect(ClusteredAgentManagerImpl.java:298)
at com.cloud.agent.manager.ClusteredAgentManagerImpl.handleDisconnectWithoutInvestigation(ClusteredAgentManagerImpl.java:287)
at com.cloud.agent.manager.AgentManagerImpl$DisconnectTask.run(AgentManagerImpl.java:958)
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:1146)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:679)
2013-07-23 15:13:13,283 DEBUG [cloud.async.AsyncJobManagerImpl] (Job-Executor-65:job-163 = [ 80888577-be56-4840-95d7-c9fe2156f3a8 ]) Done executing com.cloud.api.commands.DeleteNetscalerLoadBalancerCmd for job-163 = [ 80888577-be56-4840-95d7-c9fe2156f3a8 ]
Attaching all the logs along with db dump to the bug.
> [GSLB] NPE while removing the GSLB enabled Netscaler device
> -----------------------------------------------------------
>
> Key: CLOUDSTACK-2418
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2418
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the default.)
> Components: Network Controller
> Affects Versions: 4.2.0
> Environment: commit # 09af15035b9febe6f55e73a1389f950ab042564f
> Reporter: venkata swamybabu budumuru
> Assignee: Murali Reddy
> Fix For: 4.2.0
>
> Attachments: logs.tgz
>
>
> Steps to reproduce :
> 1. Have CloudStack with at least one advanced zone having at least one physical network
> 2. add a Netscaler to the above physical network and enable it for GSLB
> 3. delete the above Netscaler
> Observations:
> (i) Delete happens successfully but in the logs it shows NPE
> Here is the snippet from the mgmt server log
> 2013-05-09 13:33:45,798 DEBUG [agent.manager.AgentManagerImpl] (AgentTaskPool-10:null) Sending Disconnect to listener: com.cloud.consoleproxy.ConsoleProxyListener
> 2013-05-09 13:33:45,799 DEBUG [cloud.host.Status] (AgentTaskPool-10:null) Transition:[Resource state = Maintenance, Agent event = Remove, Host id = 20, name = 200-NetscalerVPXLoadBalancer-10.147.44.5]
> 2013-05-09 13:33:45,803 DEBUG [cloud.async.AsyncJobManagerImpl] (Job-Executor-145:job-289) Complete async job-289, jobStatus: 1, resultCode: 0, result: org.apache.cloudstack.api.response.SuccessResponse@6c6f4fe8
> 2013-05-09 13:33:45,805 ERROR [agent.manager.AgentManagerImpl] (AgentTaskPool-10:null) Exception caught while handling disconnect:
> java.lang.NullPointerException
> at com.cloud.host.dao.HostDaoImpl.updateState(HostDaoImpl.java:786)
> at com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
> at com.cloud.host.dao.HostDaoImpl.updateState(HostDaoImpl.java:67)
> 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:1432)
> at com.cloud.agent.manager.AgentManagerImpl.disconnectAgent(AgentManagerImpl.java:1451)
> at com.cloud.agent.manager.AgentManagerImpl.handleDisconnectWithoutInvestigation(AgentManagerImpl.java:882)
> 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:983)
> 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:1146)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
> at java.lang.Thread.run(Thread.java:679)
> 2013-05-09 13:33:45,813 DEBUG [cloud.async.AsyncJobManagerImpl] (Job-Executor-145:job-289) Done executing com.cloud.api.commands.DeleteNetscalerLoadBalancerCmd for job-289
> 2013-05-09 13:33:48,772 DEBUG [cloud.api.ApiServlet] (1394157230@qtp-1391263288-168:null) ===START=== 10.252.241.169 -- GET command=queryAsyncJobResult&jobId=ee8f7cb4-81b5-482c-a86c-7fd0fc7a494a&response=json&sessionkey=pugR8azkFvoNOD%2FvU%2B0iwMN%2FMYc%3D&_=1368101085616
> 2013-05-09 13:33:48,791 DEBUG [cloud.async.AsyncJobManagerImpl] (1394157230@qtp-1391263288-168:null) Async job-289 completed
> 2013-05-09 13:33:48,799 DEBUG [cloud.api.ApiServlet] (1394157230@qtp-1391263288-168:null) ===END=== 10.252.241.169 -- GET command=queryAsyncJobResult&jobId=ee8f7cb4-81b5-482c-a86c-7fd0fc7a494a&response=json&sessionkey=pugR8azkFvoNOD%2FvU%2B0iwMN%2FMYc%3D&_=1368101085616
> 2013-05-09 13:33:49,520 DEBUG [agent.manager.DirectAgentAttache] (DirectAgent-104:null) Seq 5-814088194: Executing request
> 2013-05-09 13:33:49,530 DEBUG [agent.manager.DirectAgentAttache] (DirectAgent-104:null) Seq 5-814088194: Response Received:
> 2013-05-09 13:33:49,531 DEBUG [agent.transport.Request] (DirectAgent-104:null) Seq 5-814088194: Processing: { Ans: , MgmtId: 7280707764394, via: 5, Ver: v1, Flags: 10, [{"UnsupportedAnswer":{"result":false,"details":"Unsupported command issued:com.cloud.agent.api.CleanupNetworkRulesCmd. Are you sure you got the right type of server?","wait":0}}] }
> Attaching all the required logs along with db dump.
--
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