You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cloudstack.apache.org by Nux! <nu...@li.nux.ro> on 2014/01/18 17:03:24 UTC

DB upgrade fails on 4.3

Hi,

DB upgrade fails from 4.2.1 to 4.3 on my setup. More info/logs here:
https://issues.apache.org/jira/browse/CLOUDSTACK-5902

Regards,
Lucian

-- 
Sent from the Delta quadrant using Borg technology!

Nux!
www.nux.ro

Re: DB upgrade fails on 4.3

Posted by Nux! <nu...@li.nux.ro>.
On 20.01.2014 09:19, Harikrishna Patnala wrote:
> Hi Nux,
> 
> Can you close the ticket if it was SNAPSHOTs issue, or you could try
> with clean right 4.2.1, set it up and try upgrade.

Closed, cheers!

-- 
Sent from the Delta quadrant using Borg technology!

Nux!
www.nux.ro

Re: DB upgrade fails on 4.3

Posted by Harikrishna Patnala <ha...@citrix.com>.
Hi Nux,

Can you close the ticket if it was SNAPSHOTs issue, or you could try with clean right 4.2.1, set it up and try upgrade.

Thanks
Harikrishna

On 19-Jan-2014, at 10:52 pm, Nux! <nu...@li.nux.ro> wrote:

> On 19.01.2014 15:41, Marcus Sorensen wrote:
>> If it helps at all, in the past when i've run into this I've edited
>> the script to comment out the line that errored, and everything prior
>> to it, then restarted the mgmt server so it could pick up the upgrade
>> where it left off. It sometimes takes 2-3 times, but you essentially
>> just skip over whatever has already been done until it works.
> 
> Thanks a lot guys for the help, it's most likely me messing with SNAPSHOTs. As I said in the ticket with a clean 4.2.1 release DB there are no issues.
> 
> Lucian
> 
> -- 
> Sent from the Delta quadrant using Borg technology!
> 
> Nux!
> www.nux.ro


Re: DB upgrade fails on 4.3

Posted by Nux! <nu...@li.nux.ro>.
On 19.01.2014 15:41, Marcus Sorensen wrote:
> If it helps at all, in the past when i've run into this I've edited
> the script to comment out the line that errored, and everything prior
> to it, then restarted the mgmt server so it could pick up the upgrade
> where it left off. It sometimes takes 2-3 times, but you essentially
> just skip over whatever has already been done until it works.

Thanks a lot guys for the help, it's most likely me messing with 
SNAPSHOTs. As I said in the ticket with a clean 4.2.1 release DB there 
are no issues.

Lucian

-- 
Sent from the Delta quadrant using Borg technology!

Nux!
www.nux.ro

Re: DB upgrade fails on 4.3

Posted by Marcus Sorensen <sh...@gmail.com>.
If it helps at all, in the past when i've run into this I've edited
the script to comment out the line that errored, and everything prior
to it, then restarted the mgmt server so it could pick up the upgrade
where it left off. It sometimes takes 2-3 times, but you essentially
just skip over whatever has already been done until it works.

On Sun, Jan 19, 2014 at 8:39 AM, Marcus Sorensen <sh...@gmail.com> wrote:
> Yes, there's no support for upgrading between dev builds, as the
> schema is changing often. Devs start fresh with the current db schema
> as they work on features. Upgrade scripts are only created between
> release schemas.
>
> On Sun, Jan 19, 2014 at 7:25 AM, Daan Hoogland <da...@gmail.com> wrote:
>> Lucian,
>>
>> I read your ticket and think that playing with a snapshot is the
>> problem most likely. To be sure you might want to setup your env
>> (including vms) on a clean 4.2.1 and see if it happens then. The db
>> upgrade scheme we use is not repeatable and on a snapshot you might
>> have missed or gotten statements extra in comparison with the release.
>>
>> I think (for a while now) we shoot device a per commit up and
>> downgrade scheme so moving from snapshot to snapshot becomes possible
>> as well. I got inspiration from the django on rail kind of frameworks
>> that can do this kind of db maintenance. Would be really cool to have
>> this.
>>
>> Your 4.2.1 snapshot most probably has the db upgrade line for this
>> 'related' column that is also in the 4.3 upgrade scripts. If you have
>> the commit you used (or maybe even with the date) you can make sure.
>>
>> regards,
>> Daan
>>
>> On Sat, Jan 18, 2014 at 5:03 PM, Nux! <nu...@li.nux.ro> wrote:
>>> Hi,
>>>
>>> DB upgrade fails from 4.2.1 to 4.3 on my setup. More info/logs here:
>>> https://issues.apache.org/jira/browse/CLOUDSTACK-5902
>>>
>>> Regards,
>>> Lucian
>>>
>>> --
>>> Sent from the Delta quadrant using Borg technology!
>>>
>>> Nux!
>>> www.nux.ro

Re: DB upgrade fails on 4.3

Posted by Marcus Sorensen <sh...@gmail.com>.
Yes, there's no support for upgrading between dev builds, as the
schema is changing often. Devs start fresh with the current db schema
as they work on features. Upgrade scripts are only created between
release schemas.

On Sun, Jan 19, 2014 at 7:25 AM, Daan Hoogland <da...@gmail.com> wrote:
> Lucian,
>
> I read your ticket and think that playing with a snapshot is the
> problem most likely. To be sure you might want to setup your env
> (including vms) on a clean 4.2.1 and see if it happens then. The db
> upgrade scheme we use is not repeatable and on a snapshot you might
> have missed or gotten statements extra in comparison with the release.
>
> I think (for a while now) we shoot device a per commit up and
> downgrade scheme so moving from snapshot to snapshot becomes possible
> as well. I got inspiration from the django on rail kind of frameworks
> that can do this kind of db maintenance. Would be really cool to have
> this.
>
> Your 4.2.1 snapshot most probably has the db upgrade line for this
> 'related' column that is also in the 4.3 upgrade scripts. If you have
> the commit you used (or maybe even with the date) you can make sure.
>
> regards,
> Daan
>
> On Sat, Jan 18, 2014 at 5:03 PM, Nux! <nu...@li.nux.ro> wrote:
>> Hi,
>>
>> DB upgrade fails from 4.2.1 to 4.3 on my setup. More info/logs here:
>> https://issues.apache.org/jira/browse/CLOUDSTACK-5902
>>
>> Regards,
>> Lucian
>>
>> --
>> Sent from the Delta quadrant using Borg technology!
>>
>> Nux!
>> www.nux.ro

Re: DB upgrade fails on 4.3

Posted by Daan Hoogland <da...@gmail.com>.
Lucian,

I read your ticket and think that playing with a snapshot is the
problem most likely. To be sure you might want to setup your env
(including vms) on a clean 4.2.1 and see if it happens then. The db
upgrade scheme we use is not repeatable and on a snapshot you might
have missed or gotten statements extra in comparison with the release.

I think (for a while now) we shoot device a per commit up and
downgrade scheme so moving from snapshot to snapshot becomes possible
as well. I got inspiration from the django on rail kind of frameworks
that can do this kind of db maintenance. Would be really cool to have
this.

Your 4.2.1 snapshot most probably has the db upgrade line for this
'related' column that is also in the 4.3 upgrade scripts. If you have
the commit you used (or maybe even with the date) you can make sure.

regards,
Daan

On Sat, Jan 18, 2014 at 5:03 PM, Nux! <nu...@li.nux.ro> wrote:
> Hi,
>
> DB upgrade fails from 4.2.1 to 4.3 on my setup. More info/logs here:
> https://issues.apache.org/jira/browse/CLOUDSTACK-5902
>
> Regards,
> Lucian
>
> --
> Sent from the Delta quadrant using Borg technology!
>
> Nux!
> www.nux.ro