From 5cf04ee03cf500f52a5d57d33da57c7522032165 Mon Sep 17 00:00:00 2001 From: Alena Prokharchyk Date: Thu, 8 Mar 2012 14:10:31 -0800 Subject: [PATCH] bug 14200: remove skip.steps config param as a part of 2.2.x-3.0 upgrade. Fixed the name for vm.destroy.forcestop config as well --- setup/db/db/schema-2214to30.sql | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/setup/db/db/schema-2214to30.sql b/setup/db/db/schema-2214to30.sql index d8d681d6b6d..83d408daec2 100755 --- a/setup/db/db/schema-2214to30.sql +++ b/setup/db/db/schema-2214to30.sql @@ -695,3 +695,8 @@ UPDATE `cloud`.`configuration` SET category = 'Usage' where category = 'Premium' ALTER TABLE `cloud`.`op_dc_vnet_alloc` ADD CONSTRAINT `fk_op_dc_vnet_alloc__data_center_id` FOREIGN KEY (`data_center_id`) REFERENCES `data_center`(`id`) ON DELETE CASCADE; ALTER TABLE `cloud`.`domain` ADD COLUMN `type` varchar(255) NOT NULL DEFAULT 'Normal' COMMENT 'type of the domain - can be Normal or Project'; + +UPDATE `cloud`.`configuration` SET name='vm.destroy.forcestop' where name='vm.destory.forcestop'; +INSERT IGNORE INTO `cloud`.`configuration` VALUES ('Advanced', 'DEFAULT', 'management-server', 'vm.destroy.forcestop', 'false', 'On destroy, force-stop takes this value'); + +DELETE FROM `cloud`.`configuration` where name='skip.steps';