Mailing-List: contact cloudstack-users-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: cloudstack-users@incubator.apache.org
Received-SPF: pass (athena.apache.org: domain of Alex.Huang@citrix.com
 designates 66.165.176.89 as permitted sender)
From: Alex Huang <Alex.Huang@citrix.com>
To: "cloudstack-users@incubator.apache.org"
	<cloudstack-users@incubator.apache.org>
Date: Thu, 10 May 2012 10:28:55 -0700
Subject: RE: DB schema upgrade script for CS 3.0.1 -> 3.0.2, probably bug.
Thread-Topic: DB schema upgrade script for CS 3.0.1 -> 3.0.2, probably bug.
Thread-Index: Ac0u0g3TRJT5E4ApQuGETLjMOX6oAgAACx+g
Message-ID: 
 <B1DF26ECC0458748AC97CECE2DA98D41011D2771EA57@SJCPMAILBOX01.citrite.net>
References: <20120510104217.72816ca1il0yqeko@webmail.soleks.com>
	<CBD142F9.4F4C%alena.prokharchyk@citrix.com>
 <CA+2rt431_oWMG7c+JFVJjcgf2r8rj2MPHPx1pNwmDbPsrngu+g@mail.gmail.com>
In-Reply-To: 
 <CA+2rt431_oWMG7c+JFVJjcgf2r8rj2MPHPx1pNwmDbPsrngu+g@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
acceptlanguage: en-US
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0

DB upgrades is one of the easiest things to unit test and there are previou=
s examples of how to unit test them.  Please do the unit testing before che=
cking them in.

--Alex

> -----Original Message-----
> From: Sheng Yang [mailto:sheng@yasker.org]
> Sent: Thursday, May 10, 2012 10:26 AM
> To: cloudstack-users@incubator.apache.org
> Cc: dan@soleks.com; Sheng Yang
> Subject: Re: DB schema upgrade script for CS 3.0.1 -> 3.0.2, probably bug=
.
>=20
> Alena,
>=20
> Sorry for the commit. As you see, that one is a revert commit. Seems I've
> used git revert without noticing there is another entry added.
>=20
> Would fix it by just drop the line.
>=20
> --
> regards
> Yang, Sheng
>=20
> On Thu, May 10, 2012 at 10:04 AM, Alena Prokharchyk
> <Alena.Prokharchyk@citrix.com> wrote:
> > On 5/10/12 10:42 AM, "dan@soleks.com" <dan@soleks.com> wrote:
> >
> >>Alena,
> >>
> >> =A0Yup, i commented out that drop from sql script. Thanks for confirma=
tion.
> >>
> >> =A0Can you please check my post on cloudstack-dev thread about public
> >>networks assigned to regular account, seems like problem still persists=
.
> >>
> >>> On 5/9/12 11:32 PM, "dan@soleks.com" <dan@soleks.com> wrote:
> >>>
> >>>>
> >>>>
> >>>>
> >>>> Hi All,
> >>>> I've found that DB schema upgrade script (CS 3.0.1 ---> CS 3.0.2)
> >>>> is trying to drop non-existing index. Log is attached.
> >>>>
> >>>> Dan.
> >>>>
> >>>>
> >>>>
> >>>>
> >>>>
> >>>> ----------------------------------------------------------------
> >>>> This message was sent using IMP, the Internet Messaging Program.
> >>>>
> >>>
> >>>
> >>>
> >>>
> >>> Sheng, this is bug introduced by your commit:
> >>>
> >>> 06c0fda878247020d79bb1008f8bf050070f1e73
> >>>
> >>>
> >>>
> >>> We are trying to drop non-existing index. To be on the safe side,
> >>> move this line to java code, and drop the key only when it exists.
> >>>
> >>> Dan, to workaround the problem on your side, do:
> >>>
> >>> * revert DB to your original version
> >>> * comment out the line "DROP INDEX `i_host__allocation_state` ON
> >>> `cloud`.`host`" in schema-301to302.sql
> >>> * being on 3.0.2, start management server once again
> >>>
> >>>
> >>> -Alena.
> >>>
> >>>
> >>>
> >>
> >>
> >>
> >>----------------------------------------------------------------
> >>This message was sent using IMP, the Internet Messaging Program.
> >>
> >
> >
> >
> >
> > Dan,
> >
> >
> > Just sent you/community the email regarding account specific public
> > range problem in multiple physical networks case.
> >
> > -Alena.
> >