incubator-cloudstack-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Alena Prokharchyk <Alena.Prokharc...@citrix.com>
Subject Re: DB schema upgrade script for CS 3.0.1 -> 3.0.2, probably bug.
Date Thu, 10 May 2012 17:33:03 GMT
On 5/10/12 10:01 AM, "Tamas Monos" <tamasm@veber.co.uk> wrote:

>Hi,
>
>Same here!
>I have fixed the script by hand and the server started but does not allow
>to login users anymore :(



Tamas, could you please file a blocker bug for "login doesn't work after
the upgrade". Provide:

* management server log file
* list all upgrade steps you've performed including the modifications
you've made to the script (did you run cloud-setup-encryption script?)
* mysql db dump taken before and after the upgrade. As the db dump can
contain sensitive info, don't attach it to the bug. Just send it to me,
and I'll erase it from my system once the issue is resolved.


-Alena.


>
>Regards
>
>Tamas Monos                                               DDI
>+44(0)2034687012
>Chief Technical                                             Office
>+44(0)2034687000
>Veber: The Hosting Specialists               Fax         +44(0)871 522
>7057
>http://www.veber.co.uk
>
>Follow us on Twitter: www.twitter.com/veberhost
>Follow us on Facebook: www.facebook.com/veberhost
>
>
>-----Original Message-----
>From: Alena Prokharchyk [mailto:Alena.Prokharchyk@citrix.com]
>Sent: 10 May 2012 17:40
>To: cloudstack-users@incubator.apache.org; Sheng Yang; dan@soleks.com
>Subject: Re: DB schema upgrade script for CS 3.0.1 -> 3.0.2, probably bug.
>
>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.
>
>
>
>



Mime
View raw message