CloudStack
  1. CloudStack
  2. CLOUDSTACK-1024

Regression: Unable to add Xenserver host with latest build

    Details

    • Type: Bug Bug
    • Status: Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: 4.1.0
    • Fix Version/s: 4.1.0
    • Component/s: None
    • Security Level: Public (Anyone can view this level - this is the default.)
    • Labels:
      None

      Description

      Find the following issue when adding a xenserver host. This is preventing us from adding xenserver hosts:

      INFO [cloud.resource.ResourceManagerImpl] (18632916@qtp-13636369-2 Trying to add a new host at http://192.168.56.101/ in data center 1
      INFO [xen.discoverer.XcpServerDiscoverer] (18632916@qtp-13636369-2 Found host devcloud ip=192.168.56.101 product version=1.6.0
      2013-01-21 11:30:32.034:WARN::Error for /client/api
      java.lang.NoSuchFieldError: _networkMgr
      at com.cloud.hypervisor.xen.discoverer.XcpServerDiscoverer.find(XcpServerDiscoverer.java:301)
      at com.cloud.resource.ResourceManagerImpl.discoverHostsFull(ResourceManagerImpl.java:700)
      at com.cloud.resource.ResourceManagerImpl.discoverHosts(ResourceManagerImpl.java:547)
      at org.apache.cloudstack.api.command.admin.host.AddHostCmd.execute(AddHostCmd.java:143)
      at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:168)
      at com.cloud.api.ApiServer.queueCommand(ApiServer.java:499)
      at com.cloud.api.ApiServer.handleRequest(ApiServer.java:350)
      at com.cloud.api.ApiServlet.processRequest(ApiServlet.java:310)
      at com.cloud.api.ApiServlet.doGet(ApiServlet.java:67)
      at javax.servlet.http.HttpServlet.service(HttpServlet.java:707)
      at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
      at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:511)
      at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:401)
      at org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java:216)
      at org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:182)
      at org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:766)
      at org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java:450)
      at org.mortbay.jetty.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:230)
      at org.mortbay.jetty.handler.HandlerCollection.handle(HandlerCollection.java:114)
      at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:152)
      at org.mortbay.jetty.Server.handle(Server.java:326)
      at org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:542)
      at org.mortbay.jetty.HttpConnection$RequestHandler.headerComplete(HttpConnection.java:928)
      at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:549)
      at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:212)
      at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:404)
      at org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:410)
      at org.mortbay.thread.QueuedThreadPool$PoolThread.run(QueuedThreadPool.java:582)

      This is broken since: http://jenkins.cloudstack.org/view/debug/job/testcloud-master-basic/ job#81

        Activity

        Chip Childers made changes -
        Status Resolved [ 5 ] Closed [ 6 ]
        Hide
        Chip Childers added a comment -

        Closing this record, since 4.1.0 is now released.

        Show
        Chip Childers added a comment - Closing this record, since 4.1.0 is now released.
        Prasanna Santhanam made changes -
        Status Open [ 1 ] Resolved [ 5 ]
        Resolution Fixed [ 1 ]
        Hide
        Prasanna Santhanam added a comment -

        The issue was the devcloud-CI hadn't been cleaning the jars in ~/.m2 before re-running the tests. This is fixed but now runtime has increased. Also fixed other issues where debug logs weren't posted as artifacts to the job when the test run failed or the management server failed to come up.

        https://github.com/vogxn/devcloud-ci/commits/master

        Show
        Prasanna Santhanam added a comment - The issue was the devcloud-CI hadn't been cleaning the jars in ~/.m2 before re-running the tests. This is fixed but now runtime has increased. Also fixed other issues where debug logs weren't posted as artifacts to the job when the test run failed or the management server failed to come up. https://github.com/vogxn/devcloud-ci/commits/master
        Prasanna Santhanam made changes -
        Priority Blocker [ 1 ] Major [ 3 ]
        Prasanna Santhanam made changes -
        Field Original Value New Value
        Assignee Chiradeep Vittal [ chiradeep ] Prasanna Santhanam [ tsp ]
        Hide
        Chiradeep Vittal added a comment -

        I don't have a problem adding DevCloud, so this could be an environment issue. This can happen if cloud-server.jar and cloud-plugin-hypervisor-xen-4.1.0-SNAPSHOT.jar are of different vintage. The field _networkManager is supplied by cloud-server

        Show
        Chiradeep Vittal added a comment - I don't have a problem adding DevCloud, so this could be an environment issue. This can happen if cloud-server.jar and cloud-plugin-hypervisor-xen-4.1.0-SNAPSHOT.jar are of different vintage. The field _networkManager is supplied by cloud-server
        Hide
        Prasanna Santhanam added a comment -

        For posterity sake: build's HEAD is at 04d93ef0aafcbea363f23d365a33a1ce4efeacd4

        Show
        Prasanna Santhanam added a comment - For posterity sake: build's HEAD is at 04d93ef0aafcbea363f23d365a33a1ce4efeacd4
        Prasanna Santhanam created issue -

          People

          • Assignee:
            Prasanna Santhanam
            Reporter:
            Prasanna Santhanam
          • Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development