On 14/02/12 09:26, Ofer Schreiber wrote: > I've recently opened > https://bugzilla.redhat.com/show_bug.cgi?id=790303 (Upgrade from > first release doesn't work). > > Generally, the DB upgrade scripts tries to run only scripts with > higher number than the last script that ran. > But if a new release includes dbscrips with lower number, they'll > never run, and cause DB upgrade issue. > Such a situation is not rare, since we cherry-pick patches into a > build branch, so the build branch might look like: > a, b, c, f, h > and the master might look like > a, b, c, d, e, f, g, h, i > > So with the current code, only scripts higher then "h" will run. > > This issue is blocking the upgrade utility of ovirt-engine. any > estimination on a fix date? > No estimation yet. We need to rethink the upgrade flow as a whole. It will take some time. Livnat

> Thanks, > Ofer Schreiber. > _______________________________________________ > Engine-devel mailing list > Engine-devel(a)ovirt.org > http://lists.ovirt.org/mailman/listinfo/engine-devel

On 14/02/12 09:36, Ofer Schreiber wrote: > > > ----- Original Message ----- >> On 14/02/12 09:26, Ofer Schreiber wrote: >>> I've recently opened >>> https://bugzilla.redhat.com/show_bug.cgi?id=790303 (Upgrade from >>> first release doesn't work). >>> >>> Generally, the DB upgrade scripts tries to run only scripts with >>> higher number than the last script that ran. >>> But if a new release includes dbscrips with lower number, they'll >>> never run, and cause DB upgrade issue. >>> Such a situation is not rare, since we cherry-pick patches into a >>> build branch, so the build branch might look like: >>> a, b, c, f, h >>> and the master might look like >>> a, b, c, d, e, f, g, h, i >>> >>> So with the current code, only scripts higher then "h" will run. >>> >>> This issue is blocking the upgrade utility of ovirt-engine. any >>> estimination on a fix date? >>> >> >> No estimation yet. >> We need to rethink the upgrade flow as a whole. It will take some >> time. >> >> Livnat > > We need some sort of estimation, as this issue might block further > releases of oVirt. > It should be within the next weeks. I don't have estimation because we haven't discussed the different solutions yet. Next oVirt release should be around May, it will be solved long before that so should not hold back the release.

>> >>> Thanks, >>> Ofer Schreiber. >>> _______________________________________________ >>> Engine-devel mailing list >>> Engine-devel(a)ovirt.org >>> http://lists.ovirt.org/mailman/listinfo/engine-devel >> >>