Got the issue, posting a patch and kick a new build. Will tell what happened soon.
On 11-Oct-2012, at 12:32 AM, Chip Childers <[email protected]> wrote: > On Wed, Oct 10, 2012 at 3:00 PM, Rohit Yadav <[email protected]> wrote: >> Just checked same case for oss also. > > Thanks for confirming Rohit. > > CLOUDSTACK-311 is now blocking the release. If people can help Rohit > sort this out, it would be appreciated. > >> On 11-Oct-2012, at 12:20 AM, Rohit Yadav <[email protected]> wrote: >> >>> Can someone quickly update me if this worked for oss build? Thanks. >>> Regards. >>> >>> On 10-Oct-2012, at 11:29 PM, Sailaja Mada <[email protected]> wrote: >>> >>>> Hi, >>>> >>>> I have installed Ubuntu MS with non-oss build >>>> CloudStack-non-OSS-4.0.0-12.tar. There is no cloudbridge db available. >>>> >>>> mysql> show databases; >>>> +--------------------+ >>>> | Database | >>>> +--------------------+ >>>> | information_schema | >>>> | cloud | >>>> | cloud_usage | >>>> | mysql | >>>> | performance_schema | >>>> | test | >>>> +--------------------+ >>>> 6 rows in set (0.00 sec) >>>> >>>> I have not configured zone yet : >>>> >>>> sailaja@UB12ASF:/$ sudo cloud-setup-databases cloud:password@localhost >>>> --deploy-as=root:password >>>> Mysql user name:cloud >>>> [ OK ] >>>> Mysql user password:password >>>> [ OK ] >>>> Mysql server ip:localhost >>>> [ OK ] >>>> Mysql server port:3306 >>>> [ OK ] >>>> Mysql root user name:root >>>> [ OK ] >>>> Mysql root user password:password >>>> [ OK ] >>>> Checking Cloud database files ... >>>> [ OK ] >>>> Checking local machine hostname ... >>>> [ OK ] >>>> Checking SELinux setup ... >>>> [ OK ] >>>> Detected local IP address as 10.102.125.220, will use as cluster >>>> management server node IP[ OK ] >>>> Preparing /etc/cloud/management/db.properties >>>> [ OK ] >>>> Applying /usr/share/cloud/setup/create-database.sql >>>> [ OK ] >>>> Applying /usr/share/cloud/setup/create-schema.sql >>>> [ OK ] >>>> Applying /usr/share/cloud/setup/create-database-premium.sql >>>> [ OK ] >>>> Applying /usr/share/cloud/setup/create-schema-premium.sql >>>> [ OK ] >>>> Applying /usr/share/cloud/setup/server-setup.sql >>>> [ OK ] >>>> Applying /usr/share/cloud/setup/templates.sql >>>> [ OK ] >>>> Applying /usr/share/cloud/setup/create-index-fk.sql >>>> [ OK ] >>>> Processing encryption ... >>>> [ OK ] >>>> Finalizing setup ... >>>> [ OK ] >>>> >>>> CloudStack has successfully initialized database, you can check your >>>> database configuration in /etc/cloud/management/db.properties >>>> >>>> >>>> Thanks and Regards, >>>> Sailaja.M >>>> >>>> -----Original Message----- >>>> From: Sudha Ponnaganti >>>> Sent: Wednesday, October 10, 2012 9:15 PM >>>> To: Rohit Yadav; Sailaja Mada >>>> Cc: Edison Su; Venkata SwamyBabu Budumuru; Chandan Purushothama; Sangeetha >>>> Hariharan; Ram Ganesh >>>> Subject: RE: [ASFCS40] Status for 4.0.0? >>>> >>>> Thanks rohit. >>>> >>>> Sailaja - pick it up and hand over to Chandan if anything is left over >>>> >>>> -----Original Message----- >>>> From: Rohit Yadav >>>> Sent: Wednesday, October 10, 2012 8:29 AM >>>> To: Sailaja Mada >>>> Cc: Sudha Ponnaganti; Edison Su; Venkata SwamyBabu Budumuru; Chandan >>>> Purushothama; Sangeetha Hariharan; Ram Ganesh >>>> Subject: Re: [ASFCS40] Status for 4.0.0? >>>> >>>> Ok Wido's is already done with his fix. I've applied the changes to the >>>> nonoss patch. >>>> >>>> Build: >>>> http://jenkins.cloudstack.org/job/build-4.0-nonoss-ubuntu1204/10/consoleFull >>>> >>>> On 10-Oct-2012, at 8:36 PM, Rohit Yadav <[email protected]> wrote: >>>> >>>>> Alright I've scheduled a new ubuntu build that will work with all nonoss >>>>> except awsapi. >>>>> Note: Wido has removed things from cloud-deps and you're required to have >>>>> a ubuntu repository configured for that to work. >>>>> >>>>> If you want take this as soon as it succeeds: >>>>> http://jenkins.cloudstack.org/job/build-4.0-nonoss-ubuntu1204/9/consol >>>>> e >>>>> >>>>> Or, we may wait till Hugo gets his packaging done for awsapi. >>>>> >>>>> Regards. >>>>> >>>>> On 10-Oct-2012, at 8:10 PM, Sailaja Mada <[email protected]> wrote: >>>>> >>>>>> Hi, >>>>>> >>>>>> I tried installation of Ubuntu MS with non-oss 8 Ubuntu Build. >>>>>> Management server is failed to start with below exception: >>>>>> >>>>>> Setup: 10.102.125.220 sailaja/freebsd >>>>>> >>>>>> 2012-10-10 20:01:51,624 INFO [utils.component.ComponentLocator] >>>>>> (main:null) Found component: com.cloud.ha.Investigator in >>>>>> com.cloud.ha.CheckOnAgentInvestigator - SimpleInvestigator >>>>>> 2012-10-10 20:01:51,624 DEBUG [utils.component.ComponentLocator] >>>>>> (main:null) Looking for class com.cloud.ha.VmwareInvestigator >>>>>> 2012-10-10 20:01:51,626 ERROR [utils.component.ComponentLocator] >>>>>> (main:null) Unable to load configuration for management-server from >>>>>> components.xml >>>>>> com.cloud.utils.exception.CloudRuntimeException: Unable to find class: >>>>>> com.cloud.ha.VmwareInvestigator >>>>>> at >>>>>> com.cloud.utils.component.ComponentLocator$XmlHandler.fillInfo(ComponentLocator.java:997) >>>>>> at >>>>>> com.cloud.utils.component.ComponentLocator$XmlHandler.startElement(ComponentLocator.java:1058) >>>>>> at >>>>>> com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.startElement(AbstractSAXParser.java:504) >>>>>> at >>>>>> com.sun.org.apache.xerces.internal.parsers.AbstractXMLDocumentParser.emptyElement(AbstractXMLDocumentParser.java:182) >>>>>> at >>>>>> com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanStartElement(XMLDocumentFragmentScannerImpl.java:1320) >>>>>> at >>>>>> com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl$FragmentContentDriver.next(XMLDocumentFragmentScannerImpl.java:2732) >>>>>> at >>>>>> com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl.next(XMLDocumentScannerImpl.java:625) >>>>>> at >>>>>> com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanDocument(XMLDocumentFragmentScannerImpl.java:488) >>>>>> at >>>>>> com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:819) >>>>>> at >>>>>> com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:748) >>>>>> at >>>>>> com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(XMLParser.java:123) >>>>>> at >>>>>> com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.parse(AbstractSAXParser.java:1208) >>>>>> at >>>>>> com.sun.org.apache.xerces.internal.jaxp.SAXParserImpl$JAXPSAXParser.parse(SAXParserImpl.java:525) >>>>>> at javax.xml.parsers.SAXParser.parse(SAXParser.java:392) >>>>>> at javax.xml.parsers.SAXParser.parse(SAXParser.java:328) >>>>>> at >>>>>> com.cloud.utils.component.ComponentLocator.parse2(ComponentLocator.java:177) >>>>>> at >>>>>> com.cloud.utils.component.ComponentLocator.parse(ComponentLocator.java:234) >>>>>> at >>>>>> com.cloud.utils.component.ComponentLocator.getLocatorInternal(ComponentLocator.java:836) >>>>>> at >>>>>> com.cloud.utils.component.ComponentLocator.getLocator(ComponentLocator.java:874) >>>>>> at >>>>>> com.cloud.servlet.CloudStartupServlet.init(CloudStartupServlet.java:48) >>>>>> at javax.servlet.GenericServlet.init(GenericServlet.java:212) >>>>>> at >>>>>> org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1206) >>>>>> at >>>>>> org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:1026) >>>>>> at >>>>>> org.apache.catalina.core.StandardContext.loadOnStartup(StandardContext.java:4421) >>>>>> at >>>>>> org.apache.catalina.core.StandardContext.start(StandardContext.java:4734) >>>>>> at >>>>>> org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:799) >>>>>> at >>>>>> org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:779) >>>>>> at >>>>>> org.apache.catalina.core.StandardHost.addChild(StandardHost.java:601) >>>>>> at >>>>>> org.apache.catalina.startup.HostConfig.deployDirectory(HostConfig.java:1079) >>>>>> at >>>>>> org.apache.catalina.startup.HostConfig.deployDirectories(HostConfig.java:1002) >>>>>> at >>>>>> org.apache.catalina.startup.HostConfig.deployApps(HostConfig.java:506) >>>>>> at org.apache.catalina.startup.HostConfig.start(HostConfig.java:1317) >>>>>> at >>>>>> org.apache.catalina.startup.HostConfig.lifecycleEvent(HostConfig.java:324) >>>>>> at >>>>>> org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:142) >>>>>> at >>>>>> org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1065) >>>>>> at org.apache.catalina.core.StandardHost.start(StandardHost.java:840) >>>>>> at >>>>>> org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1057) >>>>>> at >>>>>> org.apache.catalina.core.StandardEngine.start(StandardEngine.java:463) >>>>>> at >>>>>> org.apache.catalina.core.StandardService.start(StandardService.java:525) >>>>>> at >>>>>> org.apache.catalina.core.StandardServer.start(StandardServer.java:754) >>>>>> at org.apache.catalina.startup.Catalina.start(Catalina.java:595) >>>>>> 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:616) >>>>>> at >>>>>> org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:289) >>>>>> >>>>>> >>>>>> Thanks and Regards, >>>>>> Sailaja.M >>>>>> >>>>>> -----Original Message----- >>>>>> From: Sudha Ponnaganti >>>>>> Sent: Wednesday, October 10, 2012 7:39 PM >>>>>> To: Sailaja Mada; Rohit Yadav; Edison Su; Venkata SwamyBabu Budumuru >>>>>> Cc: Chandan Purushothama; Sangeetha Hariharan >>>>>> Subject: RE: [ASFCS40] Status for 4.0.0? >>>>>> >>>>>> Chandan will be online at 10 AM PST so be online till then and he >>>>>> will take over after that >>>>>> >>>>>> -----Original Message----- >>>>>> From: Sailaja Mada >>>>>> Sent: Wednesday, October 10, 2012 7:08 AM >>>>>> To: Sudha Ponnaganti; Rohit Yadav; Edison Su; Venkata SwamyBabu >>>>>> Budumuru >>>>>> Cc: Chandan Purushothama; Sangeetha Hariharan; Sailaja Mada >>>>>> Subject: RE: [ASFCS40] Status for 4.0.0? >>>>>> >>>>>> Hi Sudha, >>>>>> >>>>>> I will complete setup with current non-oss build and will provide the >>>>>> details to Swamy for validation. >>>>>> >>>>>> Chandan can proceed creating new setup with new build once Wido is done . >>>>>> >>>>>> Thanks and Regards, >>>>>> Sailaja.M >>>>>> >>>>>> >>>>>> -----Original Message----- >>>>>> From: Sudha Ponnaganti >>>>>> Sent: Wednesday, October 10, 2012 7:26 PM >>>>>> To: Sailaja Mada; Rohit Yadav; Edison Su; Venkata SwamyBabu Budumuru >>>>>> Cc: Chandan Purushothama; Sangeetha Hariharan >>>>>> Subject: FW: [ASFCS40] Status for 4.0.0? >>>>>> >>>>>> Sailaja, >>>>>> >>>>>> Just check basic things with current build. If this issue gets >>>>>> resolved by wido you can do reinstall Including Chandan if this goes >>>>>> beyond India time, he will pick it up >>>>>> >>>>>> Thanks >>>>>> /sudha >>>>>> >>>>>> -----Original Message----- >>>>>> From: Wido den Hollander [mailto:[email protected]] >>>>>> Sent: Wednesday, October 10, 2012 6:50 AM >>>>>> To: [email protected] >>>>>> Subject: Re: [ASFCS40] Status for 4.0.0? >>>>>> >>>>>> >>>>>> >>>>>> On 10/10/2012 03:37 PM, Sudha Ponnaganti wrote: >>>>>>> Wido, >>>>>>> >>>>>>> Do you want us to hold off validation till you are done?? >>>>>>> >>>>>> >>>>>> Yes, at least for the package installation since I'm working on that. No >>>>>> need to report any bugs for that. >>>>>> >>>>>> Wido >>>>>> >>>>>>> Thanks >>>>>>> /sudha >>>>>>> >>>>>>> -----Original Message----- >>>>>>> From: Wido den Hollander [mailto:[email protected]] >>>>>>> Sent: Wednesday, October 10, 2012 6:36 AM >>>>>>> To: [email protected] >>>>>>> Cc: [email protected] >>>>>>> Subject: Re: [ASFCS40] Status for 4.0.0? >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> Op 10 okt. 2012 om 15:14 heeft Chip Childers >>>>>>> <[email protected]> het volgende geschreven: >>>>>>> >>>>>>>> All, >>>>>>>> >>>>>>>> It appears that we have a couple of changes being made since I last >>>>>>>> looked last night: >>>>>>>> >>>>>>>> 1 - Rohit and Wido are making some modifications to the AWSAPI >>>>>>>> packaging. Guys - are we done? >>>>>>>> >>>>>>> No, not yet. I'm still seeing some file conflicts which I need to >>>>>>> resolve. >>>>>>> >>>>>>>> 2 - There is now a build job named "nightly-smoke-4.0" that is >>>>>>>> failing. What is it? Since it's new, is it's failure something >>>>>>>> that should block creating the release? FYI - our release process >>>>>>>> includes confirming that all jenkins.cs.o builds for the release >>>>>>>> branch are clear. >>>>>>>> >>>>>>>> -chip >>>>> >>>> >>> >> >>
