cloudstack-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Sebastien Goasguen <run...@gmail.com>
Subject Re: [GSOC]cannot add host with the lastest master
Date Thu, 25 Jul 2013 15:05:08 GMT
Meng, I see that you are on IRC. Try to ask there you might be able to get some direct help
which will go faster than email.

-sebastien

On Jul 24, 2013, at 1:11 PM, "Han,Meng" <menghan@ufl.edu> wrote:

> Thank you all guys!
> 
> If I am understanding this correctly, using "mvn clean install -P developer,systemvm"
will build the latest management server and systemvm code.
> This latest management server is using fully qualified class name which requires the
latest agent and system vm template to work well with it.
> 
> About the latest systemvm template, I should use cloud-install-sys-tmplt with the latest
template link (http://jenkins.cloudstack.org/view/master/job/build-systemvm-master/) to get
the  template installed.
> About the latest agent, I should use the packaging.sh scripts inside packaging directory
to get the latest agent rpm. After I got this rpm, I can use yum install to install the latest
agent.
> 
> After the above two steps I will be able to add the host to Cloudstack. Is this right?
> 
> Also in cloud.spec file (packaging/centos63/cloud.spec) the build command used is rpmbuild
mvn -Pawsapi,systemvm clean install, do I need to modify it to mvn -Pdevelper,systemvm clean
install?
> 
> When I build the rpm packages using "./packaging.sh", I get the following error:
> [INFO] Apache CloudStack AWS API Bridge .................. FAILURE [6.581s]
> [INFO] ------------------------------------------------------------------------
> [INFO] BUILD FAILURE
> [INFO] ------------------------------------------------------------------------
> [INFO] Total time: 5:29.190s
> [INFO] Finished at: Wed Jul 24 13:09:56 EDT 2013
> [INFO] Final Memory: 60M/337M
> [INFO] ------------------------------------------------------------------------
> [ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:2.5.1:compile
(default-compile) on project cloud-awsapi: Compilation failure: Compilation failure:
> [ERROR] error: error reading /root/.m2/repository/org/apache/axis2/mex/1.5.4/mex-1.5.4-impl.jar;
error in opening zip file
> [ERROR] error: error reading /root/.m2/repository/org/apache/axis2/axis2-mtompolicy/1.5.4/axis2-mtompolicy-1.5.4.jar;
error in opening zip file
> [ERROR] error: error reading /root/.m2/repository/org/apache/ws/commons/axiom/axiom-dom/1.2.10/axiom-dom-1.2.10.jar;
error in opening zip file
> [ERROR] error: error reading /root/.m2/repository/org/opensaml/opensaml1/1.1/opensaml1-1.1.jar;
error in opening zip file
> [ERROR] -> [Help 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:2.5.1:compile
(default-compile) on project cloud-awsapi: Compilation failure
> 	at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:212)
> 	at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
> 	at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
> 	at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84)
> 	at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59)
> 	at org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183)
> 	at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161)
> 	at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:318)
> 	at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:153)
> 	at org.apache.maven.cli.MavenCli.execute(MavenCli.java:555)
> 	at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:214)
> 	at org.apache.maven.cli.MavenCli.main(MavenCli.java:158)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> 	at java.lang.reflect.Method.invoke(Method.java:601)
> 	at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290)
> 	at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230)
> 	at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:414)
> 	at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:357)
> Caused by: org.apache.maven.plugin.CompilationFailureException: Compilation failure
> 	at org.apache.maven.plugin.AbstractCompilerMojo.execute(AbstractCompilerMojo.java:729)
> 	at org.apache.maven.plugin.CompilerMojo.execute(CompilerMojo.java:128)
> 	at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:106)
> 	at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208)
> 	... 19 more
> [ERROR]
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [ERROR]
> [ERROR] For more information about the errors and possible solutions, please read the
following articles:
> [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException
> [ERROR]
> [ERROR] After correcting the problems, you can resume the build with the command
> [ERROR]   mvn <goals> -rf :cloud-awsapi
> error: Bad exit status from /var/tmp/rpm-tmp.gy0E3H (%build)
> 
> 
> RPM build errors:
>    Bad exit status from /var/tmp/rpm-tmp.gy0E3H (%build)
> 
> 
> Does any one encounter this error before?
> 
> Thank you very much.
> 
> Cheers,
> Meng
> 
> 
> 
> 
> 
> 
> 
> 
> On Wed, 24 Jul 2013 10:55:52 +0000, Donal Lafferty wrote:
>> I had an offline conversation with Chiradeep to sort this out.
>> 
>> Provided the latest SystemVM code is built, there's no difficulty.
>> E.g. using "mvn clean install -P developer,systemvm"
>> See
>> https://cwiki.apache.org/confluence/display/CLOUDSTACK/How+to+build+on+master+branch
>> 
>> 
>> That said, our instructions elsewhere, and for newbies in particular,
>> are different.  I'm not sure what to do about that.
>> 
>> DL
>> 
>> 
>>> -----Original Message-----
>>> From: Donal Lafferty
>>> Sent: 24 July 2013 11:04 AM
>>> To: dev@cloudstack.apache.org
>>> Subject: RE: [GSOC]cannot add host with the lastest master
>>> 
>>> Hi Chiradeep,
>>> 
>>> Before I explore further, can I ask where
>>> "StartupSecondaryStorageCommand" mentioned in the defect
>>> https://issues.apache.org/jira/browse/CLOUDSTACK-3377 gets used?
>>> 
>>> DL
>>> 
>>> 
>>> > -----Original Message-----
>>> > From: Chiradeep Vittal [mailto:Chiradeep.Vittal@citrix.com]
>>> > Sent: 24 July 2013 6:01 AM
>>> > To: dev@cloudstack.apache.org
>>> > Subject: Re: [GSOC]cannot add host with the lastest master
>>> >
>>> > Not sure what the vintage of the systemvm has to do with it. They do
>>> > not contain the agent (Java jar files) until the systemvm is created and
>>> started.
>>> > When first started, the jar files are copied into the system vm.
>>> >
>>> >
>>> > On 7/24/13 3:41 AM, "Donal Lafferty" <donal.lafferty@citrix.com> wrote:
>>> >
>>> > >Hi Meng,
>>> > >
>>> > >You may also be having problems with your system VM.  Let me explain:
>>> > >
>>> > >The issue you see is caused by a change in JSON serialisation that
>>> > >happened in 4.2.
>>> > >
>>> > >Previously, we recorded an object's type using it's class' simple name.
>>> > >Now, we are using the full class name, which include the package. E.g.
>>> > >the serializer used to write { "StartupRoutingCommand" : ... }, but
>>> > >now it records
>>> > >{"com.cloud.agent.api.com.cloud.agent.api.StartupRoutingCommand":...}
>>> > >
>>> > >A lot of code compile against 4.1 will not be able to communicate
>>> > >with the latest management server.
>>> > >
>>> > >This means you also have to update your system VM templates.  If you
>>> > >don't, you get an error like
>>> > >https://issues.apache.org/jira/browse/CLOUDSTACK-3377
>>> > >
>>> > >Unfortunately, the default download URLs for system VMs are for 4.1.
>>> > >
>>> > >If you have not already, download the latest system VMs from
>>> > >http://jenkins.cloudstack.org/view/master/job/build-systemvm-master/
>>> > >
>>> > >Cheers,
>>> > >
>>> > >DL
>>> > >
>>> > >> -----Original Message-----
>>> > >> From: Wido den Hollander [mailto:wido@widodh.nl]
>>> > >> Sent: 23 July 2013 9:27 PM
>>> > >> To: dev@cloudstack.apache.org
>>> > >> Subject: Re: [GSOC]cannot add host with the lastest master
>>> > >>
>>> > >> Hi Meng,
>>> > >>
>>> > >> On 07/23/2013 09:28 PM, Han,Meng wrote:
>>> > >> > Hi Wei,
>>> > >> >
>>> > >> > Thank you for your reply.
>>> > >> >
>>> > >> > On Wed, 24 Jul 2013 02:08:36 +0800, Wei ZHOU wrote:
>>> > >> >> I suggest updating the agent on host as well
>>> > >> >
>>> > >> >
>>> > >> > I run yum install cloudstack-agent on the kvm host, it told
me
>>> > >> > that it's already the latest version.  I found the post
>>> > >> > here:https://issues.apache.org/jira/browse/CLOUDSTACK-3118
>>> > >> > Rajesh Battala  mentioned that he installed the latest agent
from
>>> > >> > the build CloudStack-non-OSS-MASTER-499-rhel6.3.
>>> > >> >
>>> > >>
>>> > >> This is what you run into:
>>> > >> https://issues.apache.org/jira/browse/CLOUDSTACK-3714
>>> > >>
>>> > >> > Do you know where can I get that build and how to start the
agent
>>> > >> > if I have the build(will service cloudstack-agent start do)
?
>>> > >> > I didn't find the build in
>>> > >> > https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;a=summar
>>> > >> > y
>>> > >> >
>>> > >>
>>> > >> I see you use RHEL/CentOS, with the packaging script in
>>> > >>packaging/rhel you  should be able to build RPM packages from master.
>>> > >>
>>> > >> Wido
>>> > >>
>>> > >> >
>>> > >> > Any help is appreciated.
>>> > >> >
>>> > >> > Cheers,
>>> > >> > Meng
>>> > >> >
> 


Mime
View raw message