[
https://issues.apache.org/jira/browse/CLOUDSTACK-3833?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Animesh Chaturvedi updated CLOUDSTACK-3833:
-------------------------------------------
These blockers and critical issues are resolved but not verified. Reporters of
these issues please verify the fixes and help close these issues
> 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.)
> 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,
--
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
