4.2 forward is working seamlessly inside Devcloud2 , all the system vm's are up , looking forward to debug it interactively using eclipse at port 8787.
regards, punith s On Wed, Sep 4, 2013 at 5:48 PM, Punith s <punit...@cloudbyte.com> wrote: > thanks for the info wei, > > but the thing is , i'm building all my code inside debian instance in > Devcloud2 by doing a #scp /home/cs4.2.zip 192.168.56.10:/cloudstack4.2 > so is this the way to do it ?? > > or should i git clone 4.2 and build the code in my host machine and use > Devcloud2 only for running the instances and system vm's . > because git clone was failing inside Devcloud2 . thanks, > > regards, > punith s > > > > > > > On Wed, Sep 4, 2013 at 5:29 PM, Wei ZHOU <ustcweiz...@gmail.com> wrote: > >> I think it will work if you pull the latest code of 4.2 branch >> Some commits have been cherry-picked from 4.2-forward to 4.2 branch by >> Animesh today. >> >> >> 2013/9/4 Punith s <punit...@cloudbyte.com> >> >> > i'm trying with the (4.2) zip i downloaded 4 days back , so should i try >> > with 4.2 forward ?? >> > >> > regards, >> > punith s >> > >> > >> > On Wed, Sep 4, 2013 at 5:17 PM, sebgoa <run...@gmail.com> wrote: >> > >> > > When and where did you get 4.2 ? >> > > >> > > The latest version on git should have the fix for your problem >> > > >> > > -sebastien >> > > >> > > On Sep 4, 2013, at 1:45 PM, Punith s <punit...@cloudbyte.com> wrote: >> > > >> > > > *hi folks ,* >> > > > * >> > > > * >> > > > *i'm building my cloudstack (4.2) inside DevCloud2 , i ran all the >> mvn >> > > > commands and the management jetty server is up* >> > > > * >> > > > * >> > > > *but i'm getting following exceptions is deploying the pre >> configured >> > > > infrastructure . after trying either of the commands,* >> > > > * >> > > > * >> > > > *mvn -P developer -pl tools/devcloud -Ddeploysvr** >> > > > * >> > > > * >> > > > * >> > > > *cd tools/devcloud; python ../marvin/marvin/deployDataCenter.py -i >> > > > devcloud.cfg** >> > > > * >> > > > * >> > > > * >> > > > the following log info >> > > > >> > > > WARN [xen.resource.CitrixResourceBase] (DirectAgent-1:) >> callHostPlugin >> > > > failed for cmd: setIptables with args due to There was a failure >> > > > communicating with the plugin. >> > > > WARN [xen.resource.CitrixResourceBase] (DirectAgent-1:) Unable to >> > setup >> > > > >> > > > >> > > > com.cloud.utils.exception.CloudRuntimeException: callHostPlugin >> failed >> > > for >> > > > cmd: setIptables with args due to There was a failure communicating >> > with >> > > > the plugin. >> > > > at >> > > > >> > > >> > >> com.cloud.hypervisor.xen.resource.CitrixResourceBase.callHostPlugin(CitrixResourceBase.java:4188) >> > > > >> > > > at >> > > > >> > > >> > >> com.cloud.hypervisor.xen.resource.CitrixResourceBase.setIptables(CitrixResourceBase.java:4200) >> > > > >> > > > >> > > > . >> > > > . >> > > > . >> > > > . >> > > > >> > > > >> > > > WARN [xen.discoverer.XcpServerDiscoverer] (25391925@qtp-12024104-5 >> :) >> > > > Unable to setup agent 1 due to callHostPlugin failed for cmd: >> > setIptables >> > > > with args due to There was a failure communicating with the plugin. >> > > > >> > > > >> > > > >> > > > INFO [utils.exception.CSExceptionErrorCode] >> (25391925@qtp-12024104-5 >> > :) >> > > > Could not find exception: com.cloud.exception.ConnectionException in >> > > error >> > > > code list for exceptions >> > > > WARN [agent.manager.AgentManagerImpl] (25391925@qtp-12024104-5:) >> > > Monitor >> > > > XcpServerDiscoverer_EnhancerByCloudStack_677c4d9f says there is an >> > error >> > > in >> > > > the connect process for 1 due to Reinitialize agent after setup. >> > > > >> > > > >> > > > >> > > > INFO [agent.manager.AgentManagerImpl] (25391925@qtp-12024104-5:) >> Host >> > > 1 is >> > > > disconnecting with event AgentDisconnected >> > > > >> > > > WARN [cloud.resource.ResourceManagerImpl] (25391925@qtp-12024104-5 >> :) >> > > > Unable to connect due to >> > > > >> > > > com.cloud.exception.ConnectionException: Reinitialize agent after >> > setup. >> > > > >> > > > >> > > > at >> > > > >> > > >> > >> com.cloud.hypervisor.xen.discoverer.XcpServerDiscoverer.processConnect(XcpServerDiscoverer.java:660) >> > > > >> > > > >> > > > . >> > > > . >> > > > . >> > > > . >> > > > . >> > > > . >> > > > . >> > > > . >> > > > >> > > > ERROR [cloud.api.ApiServer] (25391925@qtp-12024104-5:) unhandled >> > > exception >> > > > executing api command: addHost >> > > > >> > > > com.cloud.utils.exception.CloudRuntimeException: Cannot transit >> agent >> > > > status with event AgentDisconnected for host 1, mangement server id >> is >> > > > 8796757504512,Unable to transition to a new state from Creating via >> > > > AgentDisconnected >> > > > >> > > > >> > > > at >> > > > >> > > >> > >> com.cloud.agent.manager.AgentManagerImpl.agentStatusTransitTo(AgentManagerImpl.java:1410) >> > > > >> > > > >> > > > at >> > > > >> > > >> > >> com.cloud.resource.ResourceManagerImpl.markHostAsDisconnected(ResourceManagerImpl.java:1712) >> > > > . >> > > > . >> > > > . >> > > > . >> > > > . >> > > > . >> > > > >> > > > *is the 4.2 still fragile or can anyone tell me how to fix this ?? >> > > thanks,* >> > > > * >> > > > * >> > > > *regards,* >> > > > *punith s* >> > > > *cloudbyte* >> > > > * >> > > > * >> > > > >> > > > >> > > > On Wed, Sep 4, 2013 at 2:46 PM, Likitha Shetty < >> > > likitha.she...@citrix.com>wrote: >> > > > >> > > >> Sebastien, are you referring to the installation guide? >> > > >> >> > > >> I noticed a few defects too. I have created - >> > > >> https://issues.apache.org/jira/browse/CLOUDSTACK-4602 and updated >> - >> > > >> https://issues.apache.org/jira/browse/CLOUDSTACK-829 to track >> them. >> > > >> Please update these bugs if you see any other gaps. >> > > >> >> > > >> Thanks, >> > > >> Likitha >> > > >> >> > > >>> -----Original Message----- >> > > >>> From: sebgoa [mailto:run...@gmail.com] >> > > >>> Sent: Tuesday, September 03, 2013 5:46 PM >> > > >>> To: dev@cloudstack.apache.org >> > > >>> Subject: Re: Issues with 4.2 >> > > >>> >> > > >>> >> > > >>> On Sep 3, 2013, at 1:45 PM, sebgoa <run...@gmail.com> wrote: >> > > >>> >> > > >>>> >> > > >>>> On Sep 2, 2013, at 7:58 PM, Sebastien Goasguen <run...@gmail.com >> > >> > > >> wrote: >> > > >>>> >> > > >>>>> >> > > >>>>> On 2 Sep 2013, at 19:27, Animesh Chaturvedi >> > > >>> <animesh.chaturv...@citrix.com> wrote: >> > > >>>>> >> > > >>>>>> Sebastien >> > > >>>>>> >> > > >>>>>> DevCloud2 works with fix 1a333f36 for CLOUDSTACK-4559. The fix >> was >> > > >>>>>> put in 4.2-forward branch by Edison. I need to cherry pick this >> > and >> > > >>>>>> few other critical issues to 4.2 branch for the next VOTE on >> > Tuesday >> > > >>>>>> >> > > >>>>> >> > > >>>>> Ok i will try to cherry pick myself and test before you cut a >> new >> > RC. >> > > >>>> >> > > >>>> I cherry picked it and got devcloud running. >> > > >>>> Instance started and I was able to ssh into it. >> > > >>>> >> > > >>>> Couple strange things struck my mind: >> > > >>>> >> > > >>>> 1-in the instance view you can take a snapshot. but the snapshot >> > does >> > > >> not get >> > > >>> listed under >Storage. Only if you take a snapshot of the root >> disk >> > > from >> > > >> the >> > > >>> storage menu do you see the snapshot under >storage>view >> snapshots. >> > > >>>> >> > > >>>> 2-In the infrastructure view, under zone. If you click on the >> > devcloud >> > > >> zone you >> > > >>> now see a 'Add VMware datacenter' icon. This triggers a 'Unknown >> API >> > > >>> command: listVmwareDCs' in the mgt server log. >> > > >>>> >> > > >>>> >> > > >>>> -sebastien >> > > >>> >> > > >>> The good news is that awsapi works fine (the bad is that the >> > > >> documentation for it >> > > >>> is now wrong...) >> > > >>> >> > > >>> >> > > >>>> >> > > >>>>> >> > > >>>>> >> > > >>>>>> Animesh >> > > >>>>>> >> > > >>>>>> >> > > >>>>>> >> > > >>>>>>> -----Original Message----- >> > > >>>>>>> From: sebgoa [mailto:run...@gmail.com] >> > > >>>>>>> Sent: Monday, September 02, 2013 8:15 AM >> > > >>>>>>> To: dev@cloudstack.apache.org >> > > >>>>>>> Subject: Issues with 4.2 >> > > >>>>>>> >> > > >>>>>>> Hi, >> > > >>>>>>> >> > > >>>>>>> I spent some time testing 4.2 today: >> > > >>>>>>> >> > > >>>>>>> * Aside from the SNMP Tests errors during build time, >> > > >>>>>>> >> > > >>>>>>> * I got Devcloud up, configured the infrastructure with >> Marvin, >> > > >>>>>>> logged in on the UI all was well. >> > > >>>>>>> And then impossible to get the systemvm to start. >> > > >>>>>>> >> > > >>>>>>> Using DevCloud is our listed test procedure in the VOTE >> threads >> > so >> > > >>>>>>> it has to work. >> > > >>>>>>> >> > > >>>>>>> *Got a fresh install of 4.2 on a ubuntu 12.04, got the server >> up >> > > >>>>>>> and running and then authentication failed with: >> > > >>>>>>> >> > > >>>>>>> WARN [server.auth.SHA256SaltedUserAuthenticator] >> (934430470@qtp- >> > > >>>>>>> 324730209-0:) The stored password for admin isn't in the right >> > > >>>>>>> format for this authenticator INFO >> > [cloud.user.AccountManagerImpl] >> > > >>>>>>> (934430470@qtp-324730209-0:) User admin in domain ROOT is >> > > >>>>>>> disabled/locked (or account is disabled/locked) >> > > >>>>>>> >> > > >>>>>>> Anyone seeing this ? >> > > >>>>>>> thanks, >> > > >>>>>>> >> > > >>>>>>> -Sebastien >> > > >>>> >> > > >> >> > > >> >> > > >> > > >> > >> > >
