You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cloudstack.apache.org by "Ryan Lei (JIRA)" <ji...@apache.org> on 2013/06/28 19:11:19 UTC
[jira] [Created] (CLOUDSTACK-3278) In non-OSS build, jetty:run does
not upgrade the database to 4.1.0 and 4.1.1
Ryan Lei created CLOUDSTACK-3278:
------------------------------------
Summary: In non-OSS build, jetty:run does not upgrade the database to 4.1.0 and 4.1.1
Key: CLOUDSTACK-3278
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3278
Project: CloudStack
Issue Type: Bug
Security Level: Public (Anyone can view this level - this is the default.)
Components: Install and Setup
Affects Versions: 4.1.1
Environment: git 4.1, CentOS 6.3, Tomcat 6.0.33, non-OSS build
Reporter: Ryan Lei
Priority: Blocker
Fix For: 4.1.1
Use git 4.1 branch to build non-OSS from source with the following commands:
(1) Put the necessary jars in deps/
(2) Run deps/install-non-oss.sh with success
(3) $ mvn clean install -DskipTests=true -Dnonoss
(4) $ mvn -P developer -pl developer -Ddeploydb
(5) $ mvn -pl :cloud-client-ui jetty:run
Then I get these DB version errors which made jetty quit:
INFO [utils.component.ComponentContext] (Timer-2:) Running SystemIntegrityChecker encryptionSecretKeyChecker
INFO [utils.component.ComponentContext] (Timer-2:) Running SystemIntegrityChecker databaseIntegrityChecker
INFO [cloud.upgrade.DatabaseIntegrityChecker] (Timer-2:) Grabbing lock to check for database integrity.
INFO [cloud.upgrade.DatabaseIntegrityChecker] (Timer-2:) Performing database integrity check
INFO [utils.component.ComponentContext] (Timer-2:) Running SystemIntegrityChecker managementServerNode
INFO [utils.component.ComponentContext] (Timer-2:) Running SystemIntegrityChecker premiumDatabaseUpgradeChecker
INFO [cloud.upgrade.DatabaseUpgradeChecker] (Timer-2:) Grabbing lock to check for database upgrade.
INFO [cloud.upgrade.DatabaseUpgradeChecker] (Timer-2:) DB version = 4.0.0 Code Version = 4.1.1-SNAPSHOT
INFO [cloud.upgrade.DatabaseUpgradeChecker] (Timer-2:) Database upgrade must be performed from 4.0.0 to 4.1.1-SNAPSHOT
ERROR [cloud.upgrade.DatabaseUpgradeChecker] (Timer-2:) The end upgrade version is actually at 4.1.0 but our management server code version is at 4.1.1-SNAPSHOT
ERROR [utils.component.ComponentContext] (Timer-2:) System integrity check failed. Refuse to startup
In MySQL, the 'version' table has only one entry whose value is 4.0.0.
Manually modifying the value to 4.1.1 led to other exceptions. Looks like CloudStack "forgets" to upgrade the database.
However, the OSS build works fine. Jetty does run Upgrade40to41 and Upgrade410to411 in the log. The 'version' table has three entries.
mysql> select * from version;
+----+---------+---------------------+----------+
| id | version | updated | step |
+----+---------+---------------------+----------+
| 1 | 4.0.0 | 2013-06-28 21:58:27 | Complete |
| 2 | 4.1.0 | 2013-06-28 13:59:18 | Complete |
| 3 | 4.1.1 | 2013-06-28 13:59:18 | Complete |
+----+---------+---------------------+----------+
The non-OSS build with the 4.1.0 source code release works fine, too.
--
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