cloudstack-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Vijayendra Bhamidipati <vijayendra.bhamidip...@citrix.com>
Subject RE: Cannot deploy db on latest 4.1 branch
Date Mon, 05 Aug 2013 20:01:10 GMT
Thanks Alena! I've put in the fix, will submit the patch for review in a short while.

Cheers!
Regards,
Vijay

From: Alena Prokharchyk
Sent: Friday, August 02, 2013 4:51 PM
To: Vijayendra Bhamidipati; dev@cloudstack.apache.org
Subject: Re: Cannot deploy db on latest 4.1 branch

Happens because the management server version was changed to 4.1.2 on the 4.1 branch, but
the db upgrade path to 4.1.2 is not present in the databaseupgrade checker. Adding 411-412
db upgrade path - empty if there were no db changes between the releases- should fix this
problem.

-alena.

From: Vijayendra Bhamidipati <vijayendra.bhamidipati@citrix.com<mailto:vijayendra.bhamidipati@citrix.com>>
Date: Friday, August 2, 2013 4:32 PM
To: "dev@cloudstack.apache.org<mailto:dev@cloudstack.apache.org>" <dev@cloudstack.apache.org<mailto:dev@cloudstack.apache.org>>
Cc: Alena Prokharchyk <alena.prokharchyk@citrix.com<mailto:alena.prokharchyk@citrix.com>>
Subject: Cannot deploy db on latest 4.1 branch

I'm trying to do a simple fresh install of the mgmt. server and db using the latest 4.1 branch,
and the building of the code and the deploydb go through smoothly. However, when I attempt
to startup the mgmt. server using " mvn -pl :cloud-client-ui jetty:run", I run into a problem
with the upgrade of the db from 4.0.0 to 4.1.2:

.
.
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 databaseUpgradeChecker
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.2-SNAPSHOT
INFO  [cloud.upgrade.DatabaseUpgradeChecker] (Timer-2:) Database upgrade must be performed
from 4.0.0 to 4.1.2-SNAPSHOT
ERROR [cloud.upgrade.DatabaseUpgradeChecker] (Timer-2:) The end upgrade version is actually
at 4.1.1 but our management server code version is at 4.1.2-SNAPSHOT
ERROR [utils.component.ComponentContext] (Timer-2:) System integrity check failed. Refuse
to startup
2013-08-02 09:40:39.356:INFO::Shutdown hook executing
2013-08-02 09:40:39.357:INFO::Stopped SelectChannelConnector@0.0.0.0<mailto:SelectChannelConnector@0.0.0.0>:8080
2013-08-02 09:40:39.862:INFO:/client:Closing Spring root WebApplicationContext
.
.

It looks like there are three version numbers - db version, which is at 4.0.0 :

mysql> select * from db_version;
ERROR 1146 (42S02): Table 'cloud.db_version' doesn't exist
mysql> select * from version;
+----+---------+---------------------+----------+
| id | version | updated             | step     |
+----+---------+---------------------+----------+
|  1 | 4.0.0   | 2013-08-02 09:38:16 | Complete |
+----+---------+---------------------+----------+
1 row in set (0.01 sec)

mysql>

And then there is the "current version" which is 4.1.2, and then an "end upgrade version",
which is in a map called _upgradeMap in DatabaseUpgradeChecker.java. It looks like the last
version in this map is 4.1.1, and since that is less than 4.1.2, mgmt. server startup fails
as shown above.

Can someone please look into this and fix it? Ccing Alena as well since she's the expert on
upgrade paths for CS..


Cheers!
Regards,
Vijay


Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message