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:04:17 GMT
On 5/10/12 10:42 AM, "dan@soleks.com" <dan@soleks.com> wrote:

>Alena,
>  
>  Yup, i commented out that drop from sql script. Thanks for confirmation.
>  
>  Can 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.


Mime
View raw message