cloudstack-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Min Chen <>
Subject Re: CLOUDSTACK-1747: fresh deploydb bug in 4.1 requires cherry-pick commits from master
Date Wed, 20 Mar 2013 18:51:59 GMT
Corrected a typo, I meant "a different behavior in 4.1 from previous 4.0


On 3/20/13 11:43 AM, "Min Chen" <> wrote:

>	By reading Rohit's email and wiki, I understood current situation on this
>issue. Unlike I previously understood, this DB issue not only happens on
>dev environment, but also happens on QA/production environment as well.
>And this introduces a different behavior in 4.1 from previous 4.1 release.
>The commits mentioned in this bug will only fix dev environment, but to
>fix QA/productioin env, we need that pending feature (making
>cloud-setup-database use DatabaseCreator) to be done. We need community
>concensus whether we want to fix it in 4.1 or 4.2. Based on timeline, it
>may be wise to fix it in 4.2 and create a JIRA ticket to track this. If
>so, I still think that we need to file a doc bug to document this change
>in 4.1. 
>	Thanks
>	-min
>On 3/20/13 11:24 AM, "Min Chen" <> wrote:
>>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.
>>On 3/20/13 11:20 AM, "Rohit Yadav" <> 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.
>>>On Wed, Mar 20, 2013 at 11:46 PM, John Burwell <>
>>>> Chip,
>>>> Based on Rohit's comments, the blocking defect I raised may not be a
>>>>  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
>>>>> On Wed, Mar 20, 2013 at 11:08:01AM -0700, Min Chen wrote:
>>>>> > Hi Chip,
>>>>> >
>>>>> > I created this bug
>>>>> I noticed
>>>>>yesterday in dev setup that after running mvn -P
>>>>> developer -pl developer ­Ddeploydb, my DB is still at 4.0 version,
>>>>> expected 4.1 version. This is causing so much confusion to
>>>>> can only see our new schema introduced in 4.1 after we restart MS the
>>>>> time. This is not the expected behavior for new fresh db creation
>>>>> The correct commit is already in master, we just need to cherry-pick
>>>>> to 4.1, so I assigned this bug to you to cherry-pick those 2 commits
>>>>> master to 4.1.
>>>>> >
>>>>> > Thanks
>>>>> > -min
>>>>> Min - please see Rohit's comments in the bug.

View raw message