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 <shadow...@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 <daan.hoogl...@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! <n...@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
