Mailing-List: contact dev-help@cloudstack.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cloudstack.apache.org
Received-SPF: pass (athena.apache.org: domain of
 vijayendra.bhamidipati@citrix.com designates 66.165.176.63 as permitted
 sender)
From: Vijayendra Bhamidipati <vijayendra.bhamidipati@citrix.com>
To: "dev@cloudstack.apache.org" <dev@cloudstack.apache.org>
CC: Alena Prokharchyk <Alena.Prokharchyk@citrix.com>
Subject: Cannot deploy db on latest 4.1 branch
Thread-Topic: Cannot deploy db on latest 4.1 branch
Thread-Index: Ac6P1hyTiphrIiV3Q3C7LNhyyQ4xfQ==
Date: Fri, 2 Aug 2013 23:32:18 +0000
Message-ID: <E7693D06CA988246859053593CE40B8D12C076@SJCPEX01CL03.citrite.net>
Accept-Language: en-US
Content-Language: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0

I'm trying to do a simple fresh install of the mgmt. server and db using th=
e latest 4.1 branch, and the building of the code and the deploydb go throu=
gh smoothly. However, when I attempt to startup the mgmt. server using " mv=
n -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 SystemIntegrity=
Checker encryptionSecretKeyChecker
INFO  [utils.component.ComponentContext] (Timer-2:) Running SystemIntegrity=
Checker databaseIntegrityChecker
INFO  [cloud.upgrade.DatabaseIntegrityChecker] (Timer-2:) Grabbing lock to =
check for database integrity.
INFO  [cloud.upgrade.DatabaseIntegrityChecker] (Timer-2:) Performing databa=
se integrity check
INFO  [utils.component.ComponentContext] (Timer-2:) Running SystemIntegrity=
Checker managementServerNode
INFO  [utils.component.ComponentContext] (Timer-2:) Running SystemIntegrity=
Checker databaseUpgradeChecker
INFO  [cloud.upgrade.DatabaseUpgradeChecker] (Timer-2:) Grabbing lock to ch=
eck for database upgrade.
INFO  [cloud.upgrade.DatabaseUpgradeChecker] (Timer-2:) DB version =3D 4.0.=
0 Code Version =3D 4.1.2-SNAPSHOT
INFO  [cloud.upgrade.DatabaseUpgradeChecker] (Timer-2:) Database upgrade mu=
st be performed from 4.0.0 to 4.1.2-SNAPSHOT
ERROR [cloud.upgrade.DatabaseUpgradeChecker] (Timer-2:) The end upgrade ver=
sion 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:8080
2013-08-02 09:40:39.862:INFO:/client:Closing Spring root WebApplicationCont=
ext
.
.

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 up=
grade version", which is in a map called _upgradeMap in DatabaseUpgradeChec=
ker.java. It looks like the last version in this map is 4.1.1, and since th=
at 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