cloudstack-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sailaja Mada (JIRA)" <>
Subject [jira] [Created] (CLOUDSTACK-301) Failed to add Cluster with Nexus Switch
Date Tue, 09 Oct 2012 11:50:03 GMT
Sailaja Mada created CLOUDSTACK-301:

             Summary: Failed to add Cluster with Nexus Switch 
                 Key: CLOUDSTACK-301
             Project: CloudStack
          Issue Type: Bug
          Components: VMware
    Affects Versions: pre-4.0.0
            Reporter: Sailaja Mada
            Assignee: Devdeep Singh
            Priority: Blocker

Setup:  Management Server [ RHEL 6.3]  ,VMWARE - ESXi5   , Nexus : Nexus1000v.4.2.1.SV1.5.1

Build :CloudStack-non-OSS-106.tar 

1. Deploy VSM @ Vcenter 
2. Create port-profile sailajapp
3. Set global setting to true
4. Tried to configure advanced Zone with traffic lable as sailajapp


It Failed to add Cluster with Nexus Switch .


2012-10-09 14:10:04,301 INFO  [hypervisor.vmware.VmwareServerDiscoverer] (catalina-exec-23:null)
Detected private network label : sailajapp
2012-10-09 14:10:04,303 INFO  [hypervisor.vmware.VmwareServerDiscoverer] (catalina-exec-23:null)
Detected public network label : sailajapp
2012-10-09 14:10:04,305 INFO  [hypervisor.vmware.VmwareServerDiscoverer] (catalina-exec-23:null)
Detected guest network label : sailajapp
2012-10-09 14:10:04,310 INFO  [vmware.manager.VmwareManagerImpl] (catalina-exec-23:null) Found
empty vsmMapVO.
2012-10-09 14:10:04,313 DEBUG [vmware.resource.VmwareContextFactory] (catalina-exec-23:null)
initialize VmwareContext. url:, username: administrator,
password: f**********
2012-10-09 14:10:13,505 DEBUG [cloud.consoleproxy.ConsoleProxyManagerImpl] (consoleproxy-1:null)
Skip capacity scan due to there is no Primary Storage UPintenance mode
2012-10-09 14:10:14,053 DEBUG [network.router.VirtualNetworkApplianceManagerImpl] (RouterStatusMonitor-1:null)
Found 0 routers.
2012-10-09 14:10:19,354 INFO  [vmware.manager.VmwareManagerImpl] (catalina-exec-23:null) Calling
prepareNetwork :
2012-10-09 14:10:19,355 INFO  [vmware.manager.VmwareManagerImpl] (catalina-exec-23:null) Preparing
Network on sailajapp
2012-10-09 14:10:19,824 INFO  [] (catalina-exec-23:null) Found
Ethernet port profile sailajapp
2012-10-09 14:10:20,298 INFO  [] (catalina-exec-23:null) Port
profile cloud.private.untagged.0.1-sailajapp not found.
2012-10-09 14:10:20,298 ERROR [] (catalina-exec-23:null) Failed
to retrieve required credentials of Nexus VSM from database.
2012-10-09 14:10:20,301 WARN  [hypervisor.vmware.VmwareServerDiscoverer] (catalina-exec-23:null)
Unable to connect to Vmware vSphere server. service address:
2012-10-09 14:10:20,528 WARN  [cloud.resource.ResourceManagerImpl] (catalina-exec-23:null)
Unable to find the server resources at
2012-10-09 14:10:20,574 WARN  [api.commands.AddClusterCmd] (catalina-exec-23:null) Exception: Unable to add the external cluster
        at javax.servlet.http.HttpServlet.service(
        at javax.servlet.http.HttpServlet.service(
        at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(
        at org.apache.catalina.core.ApplicationFilterChain.doFilter(
        at org.apache.catalina.core.StandardWrapperValve.invoke(
        at org.apache.catalina.core.StandardContextValve.invoke(
        at org.apache.catalina.core.StandardHostValve.invoke(
        at org.apache.catalina.valves.ErrorReportValve.invoke(
        at org.apache.catalina.valves.AccessLogValve.invoke(
        at org.apache.catalina.core.StandardEngineValve.invoke(
        at org.apache.catalina.connector.CoyoteAdapter.service(
        at org.apache.coyote.http11.Http11NioProcessor.process(
        at org.apache.coyote.http11.Http11NioProtocol$Http11ConnectionHandler.process(
        at java.util.concurrent.ThreadPoolExecutor.runWorker(
        at java.util.concurrent.ThreadPoolExecutor$
2012-10-09 14:10:20,575 WARN  [cloud.api.ApiDispatcher] (catalina-exec-23:null) class
: Unable to add the external cluster

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:

View raw message