cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Koushik Das (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CLOUDSTACK-2414) NPE while deleting Cisco VNMC provider
Date Wed, 29 May 2013 05:46:20 GMT

    [ https://issues.apache.org/jira/browse/CLOUDSTACK-2414?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13669020#comment-13669020
] 

Koushik Das commented on CLOUDSTACK-2414:
-----------------------------------------

The delete operation completes successfully but there is a NPE in the logs. Other external
providers also follow a similar logic for the delete operation. The NPE comes as one thread
marks the host entry (corresponding to the external provider) as removed and another thread
tries to access it.
                
> NPE while deleting Cisco VNMC provider
> --------------------------------------
>
>                 Key: CLOUDSTACK-2414
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2414
>             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
>            Reporter: Sailaja Mada
>            Assignee: Koushik Das
>             Fix For: 4.2.0
>
>         Attachments: apilog.log, failedmslog, management-server.log
>
>
> Setup: Advanced Networking Zone with VMWARE Cluster 
> Steps :
> 1. Configure VMWARE Cluster with Nexus 1000v 
> 2. Add Network Service provider CiscoVnmc and add Cisco VNMC device with wrong credentials.
> 3. Delete CiscoVnmc provider 
> Observation:
> NPE during Cisco VNMC host disconnect
> 2013-05-08 22:26:34,019 DEBUG [cloud.network.NetworkUsageManagerImpl] (AgentTaskPool-2:null)
Disconnected called on 3 with status Removed
> 2013-05-08 22:26:34,019 DEBUG [agent.manager.AgentManagerImpl] (AgentTaskPool-2:null)
Sending Disconnect to listener: com.cloud.consoleproxy.ConsoleProxyListener
> 2013-05-08 22:26:34,019 DEBUG [cloud.host.Status] (AgentTaskPool-2:null) Transition:[Resource
state = Maintenance, Agent event = Remove, Host id = 3, name = Cisco VNMC Controller - 10.102.192.81]
> 2013-05-08 22:26:34,030 ERROR [agent.manager.AgentManagerImpl] (AgentTaskPool-2: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:1110)
>         at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
>         at java.lang.Thread.run(Thread.java:679)
> 2013-05-08 22:26:36,776 DEBUG [storage.secondary.SecondaryStorageManagerImpl] (secstorage-1:null)
Zone 1 is ready to launch secondary storage VM
> 2013-05-08 22:26:37,223 DEBUG [cloud.consoleproxy.ConsoleProxyManagerImpl] (consoleproxy-1:null)
Zone 1 is ready to launch console proxy

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