Thanks Rohit for the quick fix, the latest code now can pass the developer and deploydb build.
On Mon, Feb 25, 2013 at 9:54 AM, Rohit Yadav <bhais...@apache.org> wrote: > Hi Gavin, will look into this issue today. I think it's mostly a > classpath issue, for some reason the utilities/scripts/db is not on > classpath. Last time I checked, I fixed that in appConfig of > client/pom.xml. > > Regards. > > On Mon, Feb 25, 2013 at 7:19 AM, Gavin Lee <gavin....@gmail.com> wrote: >> Hi, Alex >> Using following command: >> bash$ mvn -P developer -pl developer,tools/devcloud -Ddeploydb -e -X >> >> The error log attached in this link: >> http://pastebin.com/01qjFij4 >> >> >> >> On Mon, Feb 25, 2013 at 8:59 AM, Alex Huang <alex.hu...@citrix.com> wrote: >>> Hi Gavin, >>> >>> I redeploy with commit id ac1b529f784d865a0c443c3da0367a22902ed5a2 with the >>> following two commands and it works fine. >>> >>> mvn clean install -P developer,systemvm >>> mvn -P developer -pl developer,tools/devcloud -Ddeploydb >>> >>> --Alex >>> >>>> -----Original Message----- >>>> From: Alex Huang [mailto:alex.hu...@citrix.com] >>>> Sent: Sunday, February 24, 2013 12:24 PM >>>> To: cloudstack-dev@incubator.apache.org >>>> Subject: RE: Upgrade path for db >>>> >>>> Hi Gavin, >>>> >>>> Can you send me the output from >>>> >>>> Mvn -X -e -pl developer,tools/devcloud -Ddeploydb -P developer >>>> >>>> Thanks. >>>> >>>> --Alex >>>> >>>> > -----Original Message----- >>>> > From: Gavin Lee [mailto:gavin....@gmail.com] >>>> > Sent: Sunday, February 24, 2013 6:20 AM >>>> > To: cloudstack-dev@incubator.apache.org >>>> > Subject: Re: Upgrade path for db >>>> > >>>> > Still need to copy setup/db/db to project base dir to pass following >>>> > build: >>>> > bash$ mvn -pl developer,tools/devcloud -Ddeploydb -P developer >>>> > >>>> > If not, the error message is: >>>> > >>>> > 2013-02-24 22:15:44,656 WARN [utils.script.Script] >>>> > (com.cloud.upgrade.DatabaseCreator.main():) Unable to find script >>>> > db/schema-40to410.sql >>>> > 2013-02-24 22:15:44,657 DEBUG [db.Transaction.Transaction] >>>> > (com.cloud.upgrade.DatabaseCreator.main():) Rolling back the >>>> > transaction: Time = 8 Name = >>>> > -DatabaseCreator.main:196-NativeMethodAccessorImpl.invoke0:-2- >>>> > NativeMethodAccessorImpl.invoke:39- >>>> > DelegatingMethodAccessorImpl.invoke:25-Method.invoke:597- >>>> > ExecJavaMojo$1.run:297-Thread.run:680; >>>> > called by -Transaction.rollback:890-Transaction.removeUpTo:833- >>>> > Transaction.close:657-DatabaseUpgradeChecker.upgrade:262- >>>> > DatabaseUpgradeChecker.check:357-DatabaseCreator.main:209- >>>> > NativeMethodAccessorImpl.invoke0:-2- >>>> > NativeMethodAccessorImpl.invoke:39- >>>> > DelegatingMethodAccessorImpl.invoke:25-Method.invoke:597- >>>> > ExecJavaMojo$1.run:297-Thread.run:680 >>>> > [WARNING] >>>> > java.lang.reflect.InvocationTargetException >>>> > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) >>>> > at >>>> > >>>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.j >>>> > ava:39) >>>> > at >>>> > >>>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces >>>> > sorImpl.java:25) >>>> > at java.lang.reflect.Method.invoke(Method.java:597) >>>> > at >>>> > org.codehaus.mojo.exec.ExecJavaMojo$1.run(ExecJavaMojo.java:297) >>>> > at java.lang.Thread.run(Thread.java:680) >>>> > Caused by: com.cloud.utils.exception.CloudRuntimeException: Unable to >>>> > find db/schema-40to410.sql >>>> > at >>>> > >>>> com.cloud.upgrade.dao.Upgrade40to41.getPrepareScripts(Upgrade40to41.ja >>>> > va:57) >>>> > at >>>> > >>>> com.cloud.upgrade.DatabaseUpgradeChecker.upgrade(DatabaseUpgradeCh >>>> > ecker.java:229) >>>> > at >>>> > >>>> com.cloud.upgrade.DatabaseUpgradeChecker.check(DatabaseUpgradeChec >>>> > ker.java:357) >>>> > at >>>> > com.cloud.upgrade.DatabaseCreator.main(DatabaseCreator.java:209) >>>> > >>>> > On Sun, Feb 24, 2013 at 11:31 AM, Alex Huang <alex.hu...@citrix.com> >>>> > wrote: >>>> > > I reverted 5b760f903f1a3145f62d05c1d3c142b710248026 again. It all >>>> > > works >>>> > now. >>>> > > >>>> > > --Alex >>>> > > >>>> > >> -----Original Message----- >>>> > >> From: Min Chen [mailto:min.c...@citrix.com] >>>> > >> Sent: Friday, February 22, 2013 9:46 PM >>>> > >> To: cloudstack-dev@incubator.apache.org >>>> > >> Subject: RE: Upgrade path for db >>>> > >> >>>> > >> My last commit 5b760f903f1a3145f62d05c1d3c142b710248026 is >>>> reverted >>>> > >> in master. To conclude this thread, this is not an issue for >>>> > >> developer. Just previous db behavior is changed a bit. Previously, >>>> > >> after running deployDB, we will be able to see all db schema >>>> > >> created for the branch we work on. Now with new db sql >>>> > >> reorganization, we will only be able to see all db schema created >>>> > >> after >>>> running MS first time. >>>> > >> >>>> > >> -min >>>> > >> ________________________________________ >>>> > >> From: Min Chen [min.c...@citrix.com] >>>> > >> Sent: Friday, February 22, 2013 9:27 PM >>>> > >> To: cloudstack-dev@incubator.apache.org >>>> > >> Cc: cloudstack-dev@incubator.apache.org >>>> > >> Subject: Re: Upgrade path for db >>>> > >> >>>> > >> Hi vijay, >>>> > >> >>>> > >> As I mentioned in my previous email, the commit didn't >>>> > >> completely fix the problem, which requires a manual workaround to >>>> > >> copy db folder before running deploy db. I checked it in to unblock >>>> > >> you. Since now we realized that starting MS can fix the db >>>> > >> problem, I will >>>> > revert my commit. >>>> > >> >>>> > >> -min >>>> > >> >>>> > >> Sent from my iPhone >>>> > >> >>>> > >> On Feb 22, 2013, at 7:07 PM, "Vijayendra Bhamidipati" >>>> > >> <vijayendra.bhamidip...@citrix.com> wrote: >>>> > >> >>>> > >> > I spoke too soon - I hadn't realized I was in another branch when >>>> > >> > my setup >>>> > >> worked, and the branch didn't have your fix.. now on master, I >>>> > >> actually am hitting the exception you mentioned (of not finding the >>>> > >> scripts) with the fix in place and if I revert it, I'm not seeing >>>> > >> it anymore.. any chance you may be missing something else in your >>>> setup?? >>>> > >> > >>>> > >> > Regards, >>>> > >> > Vijay >>>> > >> > >>>> > >> > -----Original Message----- >>>> > >> > From: Vijayendra Bhamidipati >>>> > >> > [mailto:vijayendra.bhamidip...@citrix.com] >>>> > >> > Sent: Friday, February 22, 2013 6:36 PM >>>> > >> > To: cloudstack-dev@incubator.apache.org >>>> > >> > Subject: RE: Upgrade path for db >>>> > >> > >>>> > >> > Hi Min! >>>> > >> > >>>> > >> > Actually I just tried this out and it did invoke the upgrade >>>> > >> > scripts when I ran >>>> > >> the jetty server to bring up the mgmt. server.. I hadn't copied >>>> > >> over the setup/db/db directory either.. did a fresh db deploy and >>>> > >> ran the >>>> > mgmt. >>>> > >> server.. thanks for fixing the db checker invocation! >>>> > >> > >>>> > >> > Cheers! >>>> > >> > Regards, >>>> > >> > Vijay >>>> > >> > >>>> > >> > >>>> > >> > -----Original Message----- >>>> > >> > From: Min Chen [mailto:min.c...@citrix.com] >>>> > >> > Sent: Friday, February 22, 2013 6:07 PM >>>> > >> > To: cloudstack-dev@incubator.apache.org >>>> > >> > Subject: Re: Upgrade path for db >>>> > >> > >>>> > >> > Yes, I am running into the same issue. The problem is that >>>> > >> > DatabaseCreator is not currently invoking DatabaseUpgradeChecker. >>>> > >> > I just checked in Commit >>>> > >> > 5b760f903f1a3145f62d05c1d3c142b710248026 to address this issue, >>>> > >> > but still >>>> > >> have one issue pending solution, that is, how to tell >>>> > >> DatabaseCreator to look into setup/db folder to look for those sql >>>> > >> script >>>> in pom.xml. >>>> > >> So far we haven't found a solution yet. A temporary workaround is >>>> > >> to copy setup/db/db to your project basedir. >>>> > >> > >>>> > >> > Thanks >>>> > >> > -min >>>> > >> > >>>> > >> > On 2/22/13 3:13 PM, "Vijayendra Bhamidipati" >>>> > >> > <vijayendra.bhamidip...@citrix.com> wrote: >>>> > >> > >>>> > >> >> How exactly are db upgrade scripts kicked off during a fresh db >>>> > >> >> install on the master branch? >>>> > >> >> >>>> > >> >> When I deploy a fresh db off the ACS master using : mvn -e -P >>>> > >> >> developer -pl developer -Ddeploydb, I don't see the tables >>>> > >> >> specified in setup/db/db/schema-40to410.sql or >>>> > setup/db/db/schema- >>>> > >> 410to420.sql >>>> > >> >> getting created. >>>> > >> >> >>>> > >> >> The version in the create-schema.sql is 4.0.0 and the same shows >>>> > >> >> up in the newly created db when I do a select * from version; >>>> > >> >> >>>> > >> >> How do I ensure that when deploying a fresh db, the tables >>>> > >> >> specified in schema40to410.sql and schema-410to420.sql get >>>> > >> >> created? >>>> > >> >> >>>> > >> >> Regards, >>>> > >> >> Vijay >>>> > >> > >>>> > >>>> > >>>> > >>>> > -- >>>> > Gavin >> >> >> >> -- >> Gavin -- Gavin
