cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Wei Zhou (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CLOUDSTACK-6195) an ACS db upgraded from Pre-4.0 version is missing unique key constraint on host_details
Date Tue, 04 Mar 2014 12:12:25 GMT

    [ https://issues.apache.org/jira/browse/CLOUDSTACK-6195?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13919320#comment-13919320
] 

Wei Zhou commented on CLOUDSTACK-6195:
--------------------------------------

https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;a=tree;f=server/src/com/cloud/upgrade/dao;h=4c697164dccd08c483b44d2ccadd31e16f04ee05;hb=6355965dcd956811dd471a9d03c73dadcf68f480

line 512 to 542 in Upgrade302to40.java.

The commit 0b31a0af6232e15618214983dfa4659b5dc6797c was commited on 2012-08-21
https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;a=commitdiff;h=0b31a0af6232e15618214983dfa4659b5dc6797c
https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;a=commitdiff;h=aec6b4af48c407a8e055656f0183f8d6eae1c9e2

Maybe your installation packages did not include it?

> 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)

Mime
View raw message