Oh, i see. That means that this issue is not only specific to dev environment, actually exists in QA environment as well. Basically QA cannot verify DB schema without starting MS once. I am consulting with Alex to see if we want to fix this in 4.1 or not.
Thanks for clarification. Chip, please hold on this. -min On 3/20/13 11:20 AM, "Rohit Yadav" <bhais...@apache.org> wrote: >For 4.1, you deploydb (that would be 4.0 schema), run mgmt server >(dbupgradechecker should upgrade to 4.1). Starting 4.2, dbcreator >would do that (like on master) and cloud-setup-databases should call >dbcreator as well. > >I tried to refactor the tool and upgrade classes, that did not work >smoothly for me so did not move refactor. Only making >cloud-setup-databases use dbcreator is pending. > >Regards. > >On Wed, Mar 20, 2013 at 11:46 PM, John Burwell <jburw...@basho.com> wrote: >> Chip, >> >> Based on Rohit's comments, the blocking defect I raised may not be a >>bug. >> I will perform a rebuild tomorrow to determine if the template_s3_ref >> table gets created properly. >> >> >> Thanks, >> -John >> >> >> On Wed, Mar 20, 2013 at 2:13 PM, Chip Childers >><chip.child...@sungard.com>wrote: >> >>> On Wed, Mar 20, 2013 at 11:08:01AM -0700, Min Chen wrote: >>> > Hi Chip, >>> > >>> > I created this bug >>>https://issues.apache.org/jira/browse/CLOUDSTACK-1747because I noticed >>>yesterday in dev setup that after running mvn -P >>> developer -pl developer Ddeploydb, my DB is still at 4.0 version, not >>> expected 4.1 version. This is causing so much confusion to developers. >>>We >>> can only see our new schema introduced in 4.1 after we restart MS the >>>first >>> time. This is not the expected behavior for new fresh db creation >>>change. >>> The correct commit is already in master, we just need to cherry-pick >>>them >>> to 4.1, so I assigned this bug to you to cherry-pick those 2 commits >>>from >>> master to 4.1. >>> > >>> > Thanks >>> > -min >>> >>> Min - please see Rohit's comments in the bug. >>>
