incubator-cloudstack-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sateesh Chodapuneedi (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CLOUDSTACK-301) Failed to add Cluster with Nexus Switch
Date Tue, 09 Oct 2012 14:31:03 GMT

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

Sateesh Chodapuneedi commented on CLOUDSTACK-301:
-------------------------------------------------

A previous commit has moved a piece of code required to add cluster with nexus switch in ResourceManagerImpl.java
to another file in plugins directory, and it's not being invoked hence forth. This commit
occurred while doing code re-org to move hypervisor specific code to "plugins/hypervisors"
directory. The issue can be readily observed in cloudstack deployment over vmware cluster
with nexus switch.

==========================================================================
commit 8197f1f07c1dc6762ea60a06e7b9bbe65ba68857
Date:   Tue Jun 26 19:48:55 2012 -0700

    moving out VMWAre and Nexus VSM support code into plugins/hypervisors/vmware
==========================================================================
                
> Failed to add Cluster with Nexus Switch 
> ----------------------------------------
>
>                 Key: CLOUDSTACK-301
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-301
>             Project: CloudStack
>          Issue Type: Bug
>          Components: VMware
>    Affects Versions: pre-4.0.0
>            Reporter: Sailaja Mada
>            Assignee: Devdeep Singh
>            Priority: Blocker
>             Fix For: 4.0.0
>
>         Attachments: api-server.log, catalina.out, management-server.log
>
>
> Setup:  Management Server [ RHEL 6.3]  ,VMWARE - ESXi5   , Nexus : Nexus1000v.4.2.1.SV1.5.1

> Build :CloudStack-non-OSS-106.tar 
> Steps:
> 1. Deploy VSM @ Vcenter 
> 2. Create port-profile sailajapp
> 3. Set global setting vmware.use.nexus.vswitch to true
> 4. Tried to configure advanced Zone with traffic lable as sailajapp
> Observation:
> It Failed to add Cluster with Nexus Switch .
> ERROR Log:
> 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: https://10.102.125.241/sdk/vimService, 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 : com.cloud.hypervisor.vmware.util.VmwareContext@40e83e52
> 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  [vmware.mo.HypervisorHostHelper] (catalina-exec-23:null)
Found Ethernet port profile sailajapp
> 2012-10-09 14:10:20,298 INFO  [vmware.mo.HypervisorHostHelper] (catalina-exec-23:null)
Port profile cloud.private.untagged.0.1-sailajapp not found.
> 2012-10-09 14:10:20,298 ERROR [vmware.mo.HypervisorHostHelper] (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: 10.102.125.241
> 2012-10-09 14:10:20,528 WARN  [cloud.resource.ResourceManagerImpl] (catalina-exec-23:null)
Unable to find the server resources at http://10.102.125.241/newdc/newcluster
> 2012-10-09 14:10:20,574 WARN  [api.commands.AddClusterCmd] (catalina-exec-23:null) Exception:
> com.cloud.exception.DiscoveryException: Unable to add the external cluster
>         at com.cloud.resource.ResourceManagerImpl.discoverCluster(ResourceManagerImpl.java:487)
>         at com.cloud.utils.db.DatabaseCallback.intercept(DatabaseCallback.java:34)
>         at com.cloud.api.commands.AddClusterCmd.execute(AddClusterCmd.java:153)
>         at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:138)
>         at com.cloud.api.ApiServer.queueCommand(ApiServer.java:543)
>         at com.cloud.api.ApiServer.handleRequest(ApiServer.java:422)
>         at com.cloud.api.ApiServlet.processRequest(ApiServlet.java:304)
>         at com.cloud.api.ApiServlet.doGet(ApiServlet.java:63)
>         at javax.servlet.http.HttpServlet.service(HttpServlet.java:617)
>         at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
>         at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
>         at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
>         at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233)
>         at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
>         at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
>         at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
>         at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:555)
>         at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
>         at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:298)
>         at org.apache.coyote.http11.Http11NioProcessor.process(Http11NioProcessor.java:889)
>         at org.apache.coyote.http11.Http11NioProtocol$Http11ConnectionHandler.process(Http11NioProtocol.java:721)
>         at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.run(NioEndpoint.java:2268)
>         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)
> 2012-10-09 14:10:20,575 WARN  [cloud.api.ApiDispatcher] (catalina-exec-23:null) class
com.cloud.api.ServerApiException : 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: http://www.atlassian.com/software/jira

Mime
View raw message