[
https://issues.apache.org/jira/browse/CLOUDSTACK-2201?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rayees Namathponnan updated CLOUDSTACK-2201:
--------------------------------------------
Attachment: CLOUDSTACK-2201.rar
> [Automation] Failed to start MS after fresh installation
> ---------------------------------------------------------
>
> Key: CLOUDSTACK-2201
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2201
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Install and Setup
> Affects Versions: 4.2.0
> Environment: CentOS 6.3 build
> Branch master
> Reporter: Rayees Namathponnan
> Priority: Blocker
> Fix For: 4.2.0
>
> Attachments: CLOUDSTACK-2201.rar
>
>
> Step 1 :Install MS from master branch build
> Step 2 : execute
> cloudstack-setup-databases cloud:password@localhost --deploy-as=root:password
> cloudstack-setup-management
> Actual result
> Failed to management server, with below error in MS log
> 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
> Is it happening due to below check-in ?
> 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.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
