create an empty upgrade path from 4.3.0 to 4.3.1 in DatabaseUpgradeChecker containing only a clss that does nothing (see 4.4.0 to 4.4.1 in the 4.4 branch for an example)
On Thu, Aug 28, 2014 at 5:14 PM, sebgoa <run...@gmail.com> wrote: > Hi, > > I am working on 4.3.1, I have set the version to 4.3.1-SNAPSHOT on the 4.3 > branch > > What do I need to do in terms of database upgrade to avoid this: > > 2014-08-28 09:33:58,698 INFO [o.a.c.s.l.CloudStackExtendedLifeCycle] > (main:null) Running system integrity checker > com.cloud.upgrade.DatabaseUpgradeChecker@495a4d80 > 2014-08-28 09:33:58,699 INFO [c.c.u.DatabaseUpgradeChecker] (main:null) > Grabbing lock to check for database upgrade. > 2014-08-28 09:33:58,735 DEBUG [c.c.u.d.VersionDaoImpl] (main:null) > Checking to see if the database is at a version before it was the version > table is created > 2014-08-28 09:33:58,768 INFO [c.c.u.DatabaseUpgradeChecker] (main:null) > DB version = 4.0.0 Code Version = 4.3.1-SNAPSHOT > 2014-08-28 09:33:58,769 INFO [c.c.u.DatabaseUpgradeChecker] (main:null) > Database upgrade must be performed from 4.0.0 to 4.3.1-SNAPSHOT > 2014-08-28 09:33:58,769 ERROR [c.c.u.DatabaseUpgradeChecker] (main:null) > The end upgrade version is actually at 4.3.0 but our management server > code version is at 4.3.1-SNAPSHOT > > > -- Daan
