You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cloudstack.apache.org by "Wei Zhou (JIRA)" <ji...@apache.org> on 2014/03/03 17:05:23 UTC
[jira] [Commented] (CLOUDSTACK-6195) an ACS db upgraded from
Pre-4.0 version is missing unique key constraint on host_details
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6195?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13918194#comment-13918194 ]
Wei Zhou commented on CLOUDSTACK-6195:
--------------------------------------
It is ok on my environment.
Here are the information of tables
mysql> show create table host_details;
+--------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| Table | Create Table |
+--------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| host_details | CREATE TABLE `host_details` (
`id` bigint(20) unsigned NOT NULL AUTO_INCREMENT,
`host_id` bigint(20) unsigned NOT NULL COMMENT 'host id',
`name` varchar(255) NOT NULL,
`value` varchar(255) NOT NULL,
PRIMARY KEY (`id`),
UNIQUE KEY `uk_host_id_name` (`host_id`,`name`),
KEY `fk_host_details__host_id` (`host_id`),
CONSTRAINT `fk_host_details__host_id` FOREIGN KEY (`host_id`) REFERENCES `host` (`id`) ON DELETE CASCADE
) ENGINE=InnoDB AUTO_INCREMENT=289 DEFAULT CHARSET=utf8 |
+--------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
1 row in set (0.01 sec)
mysql> select * from versions;
ERROR 1146 (42S02): Table 'cloud.versions' doesn't exist
mysql> select * from version;
+----+-----------------------+---------------------+----------+
| id | version | updated | step |
+----+-----------------------+---------------------+----------+
| 1 | 2.2.14.20120210102939 | 2014-01-29 16:37:41 | Complete |
| 2 | 3.0.0 | 2014-02-10 15:36:26 | Complete |
| 3 | 3.0.1 | 2014-02-10 15:36:26 | Complete |
| 4 | 3.0.2 | 2014-02-10 15:36:26 | Complete |
| 5 | 4.0.0 | 2014-02-10 15:36:26 | Complete |
| 6 | 4.1.0 | 2014-02-10 15:36:26 | Complete |
| 7 | 4.2.0 | 2014-02-10 15:36:26 | Complete |
| 8 | 4.2.1 | 2014-02-10 15:36:26 | Complete |
+----+-----------------------+---------------------+----------+
8 rows in set (0.00 sec)
> an ACS db upgraded from Pre-4.0 version is missing unique key constraint on host_details
> ----------------------------------------------------------------------------------------
>
> Key: CLOUDSTACK-6195
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6195
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the default.)
> Components: Upgrade
> Affects Versions: 4.0.0, 4.0.1, 4.0.2, 4.1.0, 4.1.1, 4.2.0, 4.2.1, 4.1.2
> Environment: Pre-4.0 db upgraded to 4.x. We have confirmed this bug in a db that started out as 2.2.14.
> Reporter: Joris van Lieshout
>
> This is the table in our 4.2.1 env that has been upgraded from 2.2.14.
> CREATE TABLE `host_details` (
> `id` bigint(20) unsigned NOT NULL AUTO_INCREMENT,
> `host_id` bigint(20) unsigned NOT NULL COMMENT 'host id',
> `name` varchar(255) NOT NULL,
> `value` varchar(255) NOT NULL,
> PRIMARY KEY (`id`),
> KEY `fk_host_details__host_id` (`host_id`),
> CONSTRAINT `fk_host_details__host_id` FOREIGN KEY (`host_id`) REFERENCES `host` (`id`) ON DELETE CASCADE
> ) ENGINE=InnoDB AUTO_INCREMENT=752966 DEFAULT CHARSET=utf8;
> And this is the table of a fresh 4.x install:
> CREATE TABLE `host_details` (
> `id` bigint(20) unsigned NOT NULL AUTO_INCREMENT,
> `host_id` bigint(20) unsigned NOT NULL COMMENT 'host id',
> `name` varchar(255) NOT NULL,
> `value` varchar(255) NOT NULL,
> PRIMARY KEY (`id`),
> UNIQUE KEY `uk_host_id_name` (`host_id`,`name`),
> KEY `fk_host_details__host_id` (`host_id`),
> CONSTRAINT `fk_host_details__host_id` FOREIGN KEY (`host_id`) REFERENCES `host` (`id`) ON DELETE CASCADE
> ) ENGINE=InnoDB AUTO_INCREMENT=242083 DEFAULT CHARSET=utf8;
> The effect of this missing bug is a lot of duplicate entries in the host_details table. The duplicate information on the host_details table causes the api call listHosts to return the same host tag multiple time (to be exact: the number of duplicate entries in the host_details table for that host).
--
This message was sent by Atlassian JIRA
(v6.2#6252)