Change on cloud.spec for the message about vhd-utils point to the new
location of cloudstack scripts
Signed-off-by: Prasanna Santhanam <tsp@apache.org>
vm deploy fails with Error "cannot find DeployPlannerSelector for vm"
adding configuration of DeployPlanSelector to nonossComponentContext.xml.in
fixed resolved
Signed-off-by: Hugo Trippaers <htrippaers@schubergphilis.com>
(cherry picked from commit c30da35811)
Signed-off-by: Hugo Trippaers <htrippaers@schubergphilis.com>
Reviewed-by: Wido (https://reviews.apache.org/r/9310)
To minimize this change, treat Debian as Ubuntu for now.
(cherry picked from commit ebb7c2e063aa2fd17955dedd993fa678556754c2)
Signed-off-by: Rohit Yadav <bhaisaab@apache.org>
It's a regression caused by:
commit 69d24545c4
Author: Murali Reddy <murali.reddy@citrix.com>
Date: Fri Feb 8 18:50:18 2013 +0530
CLOUDSTACK-1208: Failed to shutdown guest network
Firewall manager was being used instead of LoadBalancingRules manager
while applying the load balancer rules in shut down network. Changing it
to LoadBalancingRules manager.
The parameter transferre to applyRules() should be lbRules, rather than the lbs
object.
In c63dbb8804 I removed the rule from create-schema:
- `queue_proc_time` datetime COMMENT 'when processing started for the item',
But, upgrade path schema-40to410.sql had a different rule which caused the bug:
+ALTER TABLE `cloud`.`sync_queue_item` ADD `queue_proc_time` DATETIME NOT NULL
COMMENT 'when processing started for the item' AFTER `queue_proc_number`;
In this fix we just revert to whatever rule was defined in create-schema as the
developer may have forgetten to fix same rule in create-schema and upgrade path.
This commit can be reverted or the code be fixed if we want that queue_proc_time
cannot be null.
Signed-off-by: Rohit Yadav <bhaisaab@apache.org>
(cherry picked from commit 4e72d84194cb79f5f067fbe4b2c874d36d2ae0e7)
Signed-off-by: Rohit Yadav <bhaisaab@apache.org>
- Remove create-schema-view.sql, views are created when mgmt server does rolling
upgrade from 4.0.0 to 4.1.0
- Fix reference and usage of the sql file in scripts
Signed-off-by: Rohit Yadav <bhaisaab@apache.org>
(cherry picked from commit 31d6f03308)
Conflicts:
setup/db/create-schema-view.sql
Signed-off-by: Rohit Yadav <bhaisaab@apache.org>
- Fix developer prefill to use 4.0's schema
- Fix developer/pom.xml and cloud-setup-databases to not run create-schema-view,
the upgrade path is configured to do a rolling update and set it up
Signed-off-by: Rohit Yadav <bhaisaab@apache.org>
(cherry picked from commit 16e81130cc)
Signed-off-by: Rohit Yadav <bhaisaab@apache.org>