cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Venkata Siva Vijayendra Bhamidipati (JIRA)" <>
Subject [jira] [Created] (CLOUDSTACK-2867) Cannot add multiple vmware zones in vCenter
Date Wed, 05 Jun 2013 23:11:19 GMT
Venkata Siva Vijayendra Bhamidipati created CLOUDSTACK-2867:

             Summary: Cannot add multiple vmware zones in vCenter
                 Key: CLOUDSTACK-2867
             Project: CloudStack
          Issue Type: Bug
      Security Level: Public (Anyone can view this level - this is the default.)
          Components: Management Server
    Affects Versions: 4.2.0
         Environment: VMWare cloudstack deployment.
            Reporter: Venkata Siva Vijayendra Bhamidipati

Create a datacenter in vmware, say dc1, add a cluster to it, say cluster1, add one or more
hosts to cluster1. Add a zone in cloudstack, and provide dc1/cluster1 info for it. It'll go
through fine. Next, create dc2, cluster2 in vCenter with new host(s). Attempt to add a new
zone in cloudstack providing dc2/cluster2 info. It will fail with the following exception:

INFO  [cloud.configuration.ConfigurationManagerImpl] (94321089@qtp-1454176402-24:) adding
a new subnet to the network 209
WARN  [] (1538955034@qtp-1454176402-23:) Exception: This DC is already part of other CloudStack zone(s).
Cannot add this DC to more zones.
        at javax.servlet.http.HttpServlet.service(
        at javax.servlet.http.HttpServlet.service(
        at org.mortbay.jetty.servlet.ServletHolder.handle(
        at org.mortbay.jetty.servlet.ServletHandler.handle(
        at org.mortbay.jetty.servlet.SessionHandler.handle(
        at org.mortbay.jetty.handler.ContextHandler.handle(
        at org.mortbay.jetty.webapp.WebAppContext.handle(
        at org.mortbay.jetty.handler.ContextHandlerCollection.handle(
        at org.mortbay.jetty.handler.HandlerCollection.handle(
        at org.mortbay.jetty.handler.HandlerWrapper.handle(
        at org.mortbay.jetty.Server.handle(
        at org.mortbay.jetty.HttpConnection.handleRequest(
        at org.mortbay.jetty.HttpConnection$RequestHandler.headerComplete(
        at org.mortbay.jetty.HttpParser.parseNext(
        at org.mortbay.jetty.HttpParser.parseAvailable(
        at org.mortbay.jetty.HttpConnection.handle(
        at org.mortbay.thread.QueuedThreadPool$
INFO  [cloud.api.ApiServer] (1538955034@qtp-1454176402-23:) This DC is already part of other
CloudStack zone(s). Cannot add this DC to more zones.
INFO  [vmware.resource.VmwareResource] (DirectAgent-100: Executing resource

It looks like the CustomFieldDef[] key is getting defined globally for all DCs.
So once it's set to true, it's probably getting read as true for new DCs as well. Or probably
it's just that we're reading it wrongly in the mgmt server (doesn't look like that's the case

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