PremiumDatabaseUpgradeChecker on 4.2 and master branch need to be changed
as well.


2013/4/26 Rayees Namathponnan <[email protected]>

> Hi,
>
> Created new build from 4.2 branch and installed, but management server
> failed start with below error
>
>
> 2013-04-25 22:01:06,015 INFO  [utils.component.ComponentContext]
> (Timer-1:null) Running SystemIntegrityChecker premiumDatabaseUpgradeChecker
> 2013-04-25 22:01:06,015 INFO  [cloud.upgrade.DatabaseUpgradeChecker]
> (Timer-1:null) Grabbing lock to check for database upgrade.
> 2013-04-25 22:01:06,018 DEBUG [upgrade.dao.VersionDaoImpl] (Timer-1:null)
> Checking to see if the database is at a version before it was the version
> table is created
> 2013-04-25 22:01:06,030 INFO  [cloud.upgrade.DatabaseUpgradeChecker]
> (Timer-1:null) DB version = 4.0.0 Code Version = 4.2.0-SNAPSHOT
> 2013-04-25 22:01:06,030 INFO  [cloud.upgrade.DatabaseUpgradeChecker]
> (Timer-1:null) Database upgrade must be performed from 4.0.0 to
> 4.2.0-SNAPSHOT
> 2013-04-25 22:01:06,030 ERROR [cloud.upgrade.DatabaseUpgradeChecker]
> (Timer-1:null) The end upgrade version is actually at 4.1.0 but our
> management server code version is at 4.2.0-SNAPSHOT
> 2013-04-25 22:01:06,036 ERROR [utils.component.ComponentContext]
> (Timer-1:null) System integrity check failed. Refuse to startup
>
>
>
> Yesterday's build created from git number
> 762977d7c6f35c6f412dddc87a832a0bafc4db87,works fine.
>
>
>
> Might got broken after below check-in, but I am not sure
>
> Commit 099677a1244cd55fb98d3c40ee7881223dd9ac7c by chip.childers
> CLOUDSTACK-2172: adding database upgrade to 4.1.0 in
> PremiumDatabaseUpgradeChecker
>
> Add migration to 4.1.0 in the PremiumDatabaseUpgradeChecker, like in the
> DatabaseUpgradeChecker.
>
> I opened the ticket CS 2172, and this fix corrects the issue.
> Regards.
>
> Signed-off-by: Chip Childers <[email protected]>
>
>
> Regards,
> Rayees
>
>

Reply via email to