[
https://issues.apache.org/jira/browse/CLOUDSTACK-1024?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13559805#comment-13559805
]
Prasanna Santhanam commented on CLOUDSTACK-1024:
------------------------------------------------
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
> Regression: Unable to add Xenserver host with latest build
> ----------------------------------------------------------
>
> Key: CLOUDSTACK-1024
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1024
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Affects Versions: 4.1.0
> Reporter: Prasanna Santhanam
> Assignee: Prasanna Santhanam
> Fix For: 4.1.0
>
>
> 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
--
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
