cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sailaja Mada (JIRA)" <j...@apache.org>
Subject [jira] [Created] (CLOUDSTACK-2558) Nexus configuration cleanup is not done when there is failure while adding the Nexus enabled VMWARE cluster which is causing for NPE while readding the cluster with same configuration details
Date Fri, 17 May 2013 09:15:16 GMT
Sailaja Mada created CLOUDSTACK-2558:
----------------------------------------

             Summary: Nexus configuration cleanup is not done when there is failure while
adding the Nexus enabled VMWARE cluster which is causing for NPE while readding the cluster
with same configuration details 
                 Key: CLOUDSTACK-2558
                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2558
             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


Setup:  Advanced Networking VMWARE Nexus Enabled Cluster .

1. While adding the cluster , it failed with wrong DataCenter/Cluster name . 
2. Tried to add the cluster again with the same details. It failed with NPE.

Observation.

1. When there is failure in cluster addition , Nexus configuration Clean up  is not done .
So when tried to reuse the same it failed with NPE.

2. Nexus configuration cleanup is not done when there is failure while adding the Nexus enabled
VMWARE cluster which is causing for NPE while readding the cluster with same configuration
details 


2013-05-17 14:32:25,882 DEBUG [cloud.api.ApiServlet] (catalina-exec-7:null) ===START===  10.144.6.19
-- GET  command=addCluster&zoneId=43d81d64-0e93-4ef7-839d-34cb9bd3a1b9&hypervisor=VMware&clustertype=ExternalManaged&podId=cb4dc8b9-079a-4222-a07a-9fb1c92c9304&cpuovercommitratio=1&memoryovercommitratio=1&username=administrator&publicvswitchtype=nexusdvs&publicvswitchname=nexuspp&guestvswitchtype=nexusdvs&guestvswitchname=nexuspp&vsmipaddress=10.102.192.71&vsmusername=admin&vsm&url=http%3A%2F%2F10.102.192.248%2Fvnmcdc%2Fvnmcc&clustername=10.102.192.248%2Fvnmcdc%2Fvnmcc&response=json&sessionkey=DyVgPLt%2Bl958PAh6d3eYzJNyHLw%3D&_=1368781495812
2013-05-17 14:32:25,997 INFO  [hypervisor.vmware.VmwareServerDiscoverer] (catalina-exec-7:null)
Discover host. dc: 1, pod: 1, cluster: 2, uri host: 10.102.192.248
2013-05-17 14:32:26,618 ERROR [network.element.CiscoNexusVSMElement] (catalina-exec-7:null)
Failed to add cluster: specified Nexus VSM is already associated with another cluster
2013-05-17 14:32:26,768 ERROR [cloud.api.ApiServer] (catalina-exec-7:null) unhandled exception
executing api command: addCluster
java.lang.NullPointerException
        at com.cloud.network.element.CiscoNexusVSMElement.validateVsmCluster(CiscoNexusVSMElement.java:288)
        at com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
        at com.cloud.hypervisor.vmware.VmwareServerDiscoverer.find(VmwareServerDiscoverer.java:269)
        at com.cloud.resource.ResourceManagerImpl.discoverCluster(ResourceManagerImpl.java:563)
        at com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
        at org.apache.cloudstack.api.command.admin.cluster.AddClusterCmd.execute(AddClusterCmd.java:208)
        at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:155)
        at com.cloud.api.ApiServer.queueCommand(ApiServer.java:519)
        at com.cloud.api.ApiServer.handleRequest(ApiServer.java:369)
        at com.cloud.api.ApiServlet.processRequest(ApiServlet.java:304)
        at com.cloud.api.ApiServlet.doGet(ApiServlet.java:66)
        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)
2013-05-17 14:32:26,771 DEBUG [cloud.api.ApiServlet] (catalina-exec-7:null) ===END===  10.144.6.19
-- GET  command=addCluster&zoneId=43d81d64-0e93-4ef7-839d-34cb9bd3a1b9&hypervisor=VMware&clustertype=ExternalManaged&podId=cb4dc8b9-079a-4222-a07a-9fb1c92c9304&cpuovercommitratio=1&memoryovercommitratio=1&username=administrator&publicvswitchtype=nexusdvs&publicvswitchname=nexuspp&guestvswitchtype=nexusdvs&guestvswitchname=nexuspp&vsmipaddress=10.102.192.71&vsmusername=admin&vsm&url=http%3A%2F%2F10.102.192.248%2Fvnmcdc%2Fvnmcc&clustername=10.102.192.248%2Fvnmcdc%2Fvnmcc&response=json&sessionkey=DyVgPLt%2Bl958PAh6d3eYzJNyHLw%3D&_=1368781495812






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