cloudstack-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Vijayendra Bhamidipati <vijayendra.bhamidip...@citrix.com>
Subject RE: Unresolved compilation problem?
Date Mon, 01 Jul 2013 21:40:24 GMT
Hi Hugo,

Looks like it was just due to some stale files - probably mvn clean has some issue where it
isn't cleaning them up - I nuked and recreated my workspace and the cluster addition went
through. Thanks for the prompt response!

Cheers!
Regards,
Vijay

-----Original Message-----
From: Hugo Trippaers [mailto:trippie@gmail.com] 
Sent: Monday, July 01, 2013 1:39 PM
To: dev@cloudstack.apache.org
Cc: dev@cloudstack.apache.org
Subject: Re: Unresolved compilation problem?

Heya,

I've made some changes to this function to support multiple types of broadcast domain types.
So I had to add a dependency to the Pom to get the BroadcastDomainType enum.

This probably was not properly updated until you did a full recompile.

Cheers,

Hugo 

Sent from my iPhone

On 1 jul. 2013, at 22:21, Vijayendra Bhamidipati <vijayendra.bhamidipati@citrix.com>
wrote:

> I'm running into this exception when trying to add a vmware cluster on top of latest
master:
> 
> 
> INFO  [cloud.configuration.ConfigurationManagerImpl] 
> (829088401@qtp-729217986-4:) adding a new subnet to the network 200 
> INFO  [hypervisor.vmware.VmwareServerDiscoverer] 
> (1175658854@qtp-729217986-5:) Discover host. dc: 1, pod: 1, cluster: 
> 1, uri host: 10.223.52.61
> 2013-07-01 06:52:24.507:WARN::Error for /client/api
> java.lang.Error: Unresolved compilation problem: |?The method prepareNetwork(String,
String, HostMO, String, Integer, Integer, long, boolean, BroadcastDomainType) from the type
HypervisorHostHelper refers to the missing type BroadcastDomainType|
>        at com.cloud.hypervisor.vmware.manager.VmwareManagerImpl.prepareHost(VmwareManagerImpl.java:351)
>        at com.cloud.hypervisor.vmware.manager.VmwareManagerImpl.addHostToPodCluster(VmwareManagerImpl.java:397)
>        at com.cloud.hypervisor.vmware.VmwareServerDiscoverer.find(VmwareServerDiscoverer.java:312)
>        at com.cloud.resource.ResourceManagerImpl.discoverCluster(ResourceManagerImpl.java:538)
>        at com.cloud.resource.ResourceManagerImpl_EnhancerByCloudStack_84a53fa0.CGLIB$discoverCluster$29(<generated>)
>        at com.cloud.resource.ResourceManagerImpl_EnhancerByCloudStack_84a53fa0_FastClassByCloudStack_84071e69.invoke(<generated>)
>        at net.sf.cglib.proxy.MethodProxy.invokeSuper(MethodProxy.java:228)
>        at com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
>        at com.cloud.resource.ResourceManagerImpl_EnhancerByCloudStack_84a53fa0.discoverCluster(<generated>)
>        at org.apache.cloudstack.api.command.admin.cluster.AddClusterCmd.execute(AddClusterCmd.java:204)
>        at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:155)
>        at com.cloud.api.ApiServer.queueCommand(ApiServer.java:528)
>        at com.cloud.api.ApiServer.handleRequest(ApiServer.java:371)
>        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: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.ja
> va:582)
> 
> 
> 
> I believe this could be caused by stale eclipse generated compile time files, so I did
a mvn clean and retried the compilation, which went through fine, and the mgmt. server restarted
up fine, so what am I missing? Any ideas?
> 
> 
> Regards,
> Vijay

Mime
View raw message