Please disregard. The issue related to an attempt of being able to run multiple versions of dev CS on the same host and altering a database name from "cloud" to "cloud42" or something else. Needless to say all component like cloud_usage and cloudbridge - must remain default.
-----Original Message----- From: Musayev, Ilya [mailto:imusa...@webmd.net] Sent: Tuesday, February 26, 2013 3:56 PM To: cloudstack-dev@incubator.apache.org Subject: RE: [ACS][BUG] Master build breaks due to sql updates Looks like the initial db version was set to 4.0.0 on developer/target/db/create-schema.sql Change From INSERT INTO `version` (`version`, `updated`, `step`) VALUES('4.0.0', now(), 'Complete'); To INSERT INTO `version` (`version`, `updated`, `step`) VALUES('4.2.0', now(), 'Complete'); Deploys db successfully, I now wonder if there is a sql patch update I could have missed.. Whoever knows, please confirm Thanks -ilya -----Original Message----- From: Musayev, Ilya [mailto:imusa...@webmd.net] Sent: Tuesday, February 26, 2013 3:41 PM To: cloudstack-dev@incubator.apache.org Subject: [ACS][BUG] Master build breaks due to sql updates Hi All, Master build breaks, as com.cloud.upgrade.DatabaseUpgradeChecker attempts to update/patch a new database with older versions. I'm a bit puzzled as to why a fresh installed DB has to be updated. In either way, it looks like DatabaseUpgradeChecker creates a dir "db" within developer/ target/db with many update sql files going from versions of 2.x to 4.1 Is this an expected behavior to create a fresh database and then layer on the sql patches on top? Or did the mechanism that checks if DB update is necessary - stopped functioning? To reproduce this issue, initiate a fresh build as of 02/26/13, run through install and execute db deployment. mvn -P developer -pl developer -Ddeploydb Thanks ilya
