cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CLOUDSTACK-3612) 3.0.6 to ASF 4.2 Upgrade: Database Schema Inconsistencies on the Upgraded Setup
Date Fri, 09 Aug 2013 23:48:48 GMT

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

ASF subversion and git services commented on CLOUDSTACK-3612:
-------------------------------------------------------------

Commit ad508b7232e28ca02683bd8b60268cb87c71e36a in branch refs/heads/4.2 from [~frank.zhang]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=ad508b7 ]

CLOUDSTACK-38333.0.6 to ASF 4.2 Upgrade: "cloud" Database Schema Inconsistencies on the Upgraded
Setup - Tables "baremetal_dhcp_devices" and "baremetal_pxe_devices"

CloudStack CLOUDSTACK-3612
3.0.6 to ASF 4.2 Upgrade: Database Schema Inconsistencies on the Upgraded Setup

                
> 3.0.6 to ASF 4.2 Upgrade: Database Schema Inconsistencies on the Upgraded Setup
> -------------------------------------------------------------------------------
>
>                 Key: CLOUDSTACK-3612
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3612
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: Upgrade
>    Affects Versions: 4.2.0
>            Reporter: Chandan Purushothama
>            Assignee: frank zhang
>            Priority: Critical
>             Fix For: 4.2.0
>
>
> Table 1: baremetal_dhcp_devices
> On ASF 4.2 Setup:
>  `nsp_id` bigint(20) UNSIGNED DEFAULT NULL,
>  `pod_id` bigint(20) UNSIGNED DEFAULT NULL,
>  `device_type` varchar(255) DEFAULT NULL,
>  `physical_network_id` bigint(20) UNSIGNED DEFAULT NULL,
>  `host_id` bigint(20) UNSIGNED DEFAULT NULL,
> On the 4.2 Upgraded Setup: 
>  `nsp_id` bigint(20) UNSIGNED NOT NULL,
>  `pod_id` bigint(20) UNSIGNED NOT NULL,
>  `device_type` varchar(255) NOT NULL,
>  `physical_network_id` bigint(20) UNSIGNED NOT NULL,
>  `host_id` bigint(20) UNSIGNED NOT NULL,
> Table 2: baremetal_pxe_devices
> On ASF 4.2 Setup:
>  `nsp_id` bigint(20) UNSIGNED DEFAULT NULL,
>  `device_type` varchar(255) DEFAULT NULL,
>  `physical_network_id` bigint(20) UNSIGNED DEFAULT NULL,
>  `host_id` bigint(20) UNSIGNED DEFAULT NULL,
> On the 4.2 Upgraded Setup:
>  `nsp_id` bigint(20) UNSIGNED NOT NULL,
>  `device_type` varchar(255) NOT NULL,
>  `physical_network_id` bigint(20) UNSIGNED NOT NULL,
>  `host_id` bigint(20) UNSIGNED NOT NULL,
> Table 3: netscaler_pod_ref
> On ASF 4.2 Setup:
> Present on the Setup
> Missing on the Upgraded Setup.
> Table 4: nicira_nvp_nic_map
> On ASF 4.2 Setup:
> Constraint:
> ALTER TABLE `cloud`.`nicira_nvp_nic_map` ADD CONSTRAINT `fk_nicira_nvp_nic_map__nic`
>  FOREIGN KEY ( `nic` ) REFERENCES `nics` ( `uuid` ) ON DELETE CASCADE;
> On the 4.2 Upgraded Setup:
> No such constraint
> Table 5: router_network_ref
> On ASF 4.2 Setup:
> Constraint:
> ALTER TABLE `cloud`.`router_network_ref` ADD CONSTRAINT `fk_router_network_ref__router_id`
>  FOREIGN KEY ( `router_id` ) REFERENCES `domain_router` ( `id` ) ON DELETE CASCADE;
> On the 4.2 Upgraded Setup:
> No such constraint
> Table 6: sync_queue
> On ASF 4.2 Setup:
>   `queue_size` smallint(6) NOT NULL DEFAULT '0',
>  `queue_size_limit` smallint(6) NOT NULL DEFAULT '1',
> On the 4.2 Upgraded Setup: 
>  `queue_size` smallint(6) DEFAULT '0',
>  `queue_size_limit` smallint(6) DEFAULT '1',
> Table 7: usage_event
> On ASF 4.2 Setup:
> no virtual_size column
> On the 4.2 Upgraded Setup: 
>  `virtual_size` bigint(20) UNSIGNED DEFAULT NULL,
> Table 8: volumes
> On ASF 4.2 Setup:
> no iso_id column
> On the 4.2 Upgraded Setup: 
>  `iso_id` bigint(20) UNSIGNED DEFAULT NULL,

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message