From e358c45e8a822ec66286f650f218486167797273 Mon Sep 17 00:00:00 2001 From: frank Date: Thu, 8 Mar 2012 10:24:28 -0800 Subject: [PATCH] Bug 14170 - 2.2.14(KVM) - 3.0.1 Upgrade: DB inconsistencies after Upgrade default resource_state should be Enabled --- setup/db/create-schema.sql | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/setup/db/create-schema.sql b/setup/db/create-schema.sql index 771e0c7c867..5a5be19b135 100755 --- a/setup/db/create-schema.sql +++ b/setup/db/create-schema.sql @@ -785,7 +785,7 @@ CREATE TABLE `cloud`.`host` ( `created` datetime COMMENT 'date the host first signed on', `removed` datetime COMMENT 'date removed if not null', `update_count` bigint unsigned NOT NULL DEFAULT 0 COMMENT 'atomic increase count making status update operation atomical', - `resource_state` varchar(32) NOT NULL DEFAULT 'Disabled' COMMENT 'Is this host enabled for allocation for new resources', + `resource_state` varchar(32) NOT NULL DEFAULT 'Enabled' COMMENT 'Is this host enabled for allocation for new resources', PRIMARY KEY (`id`), INDEX `i_host__removed`(`removed`), INDEX `i_host__last_ping`(`last_ping`),