cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chandan Purushothama (JIRA)" <j...@apache.org>
Subject [jira] [Created] (CLOUDSTACK-3833) 3.0.6 to ASF 4.2 Upgrade: "cloud" Database Schema Inconsistencies on the Upgraded Setup - Tables "baremetal_dhcp_devices" and "baremetal_pxe_devices"
Date Fri, 26 Jul 2013 00:07:48 GMT
Chandan Purushothama created CLOUDSTACK-3833:
------------------------------------------------

             Summary: 3.0.6 to ASF 4.2 Upgrade: "cloud" Database Schema Inconsistencies on
the Upgraded Setup - Tables "baremetal_dhcp_devices" and "baremetal_pxe_devices"
                 Key: CLOUDSTACK-3833
                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3833
             Project: CloudStack
          Issue Type: Bug
      Security Level: Public (Anyone can view this level - this is the default.)
            Reporter: Chandan Purushothama
            Priority: Critical



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,


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