[
https://issues.apache.org/jira/browse/CLOUDSTACK-2409?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13655518#comment-13655518
]
Koushik Das commented on CLOUDSTACK-2409:
-----------------------------------------
Branch: refs/heads/master
Commit: 80720dc4ace487647279c338005aa8ea9ffcc627
Parents: 0749013
Author: Koushik Das <[email protected]>
Authored: Sun May 12 17:00:48 2013 +0530
Committer: Koushik Das <[email protected]>
Committed: Sun May 12 17:00:48 2013 +0530
> Cisco VNMC Access credentials validatation is not enabled with
> addCiscoVnmcResource
> ------------------------------------------------------------------------------------
>
> Key: CLOUDSTACK-2409
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2409
> 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
>
>
> Setup: Advanced Networking Zone with VMWARE Cluster
> Steps :
> 1. Configure VMWARE Cluster with Nexus 1000v
> 2.Try to Add Network Service provider CiscoVnmc with wrong credentials
> Observation:
> 1) Cisco VNMC Access credentials validatation is not enabled with
> addCiscoVnmcResource
> 2) CS allowed to add VNMC provider with wrong password
> Later when CS tried to get the status of the host , it started printing login
> failed to VNMC in the logs.
> 2013-05-08 22:22:49,927 ERROR [network.resource.CiscoVnmcResource]
> (DirectAgent-25:null) Login to Vnmc failed
> com.cloud.utils.exception.ExecutionException: No route to host
> at
> com.cloud.network.cisco.CiscoVnmcConnectionImpl.sendRequest(CiscoVnmcConnectionImpl.java:1332)
> at
> com.cloud.network.cisco.CiscoVnmcConnectionImpl.login(CiscoVnmcConnectionImpl.java:167)
> at
> com.cloud.network.resource.CiscoVnmcResource.refreshVnmcConnection(CiscoVnmcResource.java:238)
> at
> com.cloud.network.resource.CiscoVnmcResource.getCurrentStatus(CiscoVnmcResource.java:202)
> at
> com.cloud.agent.manager.DirectAgentAttache$PingTask.run(DirectAgentAttache.java:137)
> at
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
> at
> java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:351)
> at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:178)
> at
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:165)
> at
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:267)
> 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:22:49,929 WARN [agent.manager.DirectAgentAttache]
> (DirectAgent-25:null) Unable to get current status on 3
> 2013-05-08 22:22:49,933 INFO [agent.manager.AgentManagerImpl]
> (AgentTaskPool-9:null) Investigating why host 3 has disconnected with event
> AgentDisconnected
> 2013-05-08 22:22:49,934 DEBUG [agent.manager.AgentManagerImpl]
> (AgentTaskPool-9:null) checking if agent (3) is alive
> 2013-05-08 22:22:49,938 DEBUG [agent.transport.Request]
> (AgentTaskPool-9:null) Seq 3-1050148872: Sending { Cmd , MgmtId:
> 214053811722752, via: 3, Ver: v1, Flags: 100011,
> [{"CheckHealthCommand":{"wait":50}}] }
--
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
