Hi, The latest 3.0.x and 3.0.3 branches have db changes made in them. If you do not intend to redeploy the cloud database, please execute the following DMLs in the `cloud` db:
CREATE TABLE `cloud`.`cluster_vsm_map` ( `cluster_id` bigint unsigned NOT NULL, `vsm_id` bigint unsigned NOT NULL, PRIMARY KEY (`cluster_id`) ) ENGINE=InnoDB DEFAULT CHARSET=utf8; CREATE TABLE `cloud`.`virtual_supervisor_module` ( `id` bigint unsigned NOT NULL auto_increment COMMENT 'id', `uuid` varchar(40), `host_id` bigint NOT NULL, `vsm_name` varchar(255), `username` varchar(255) NOT NULL, `password` varchar(255) NOT NULL, `ipaddr` varchar(80) NOT NULL, `management_vlan` int(32), `control_vlan` int(32), `packet_vlan` int(32), `storage_vlan` int(32), `vsm_domain_id` bigint unsigned, `config_mode` varchar(20), `config_state` varchar(20), `vsm_device_state` varchar(20) NOT NULL, PRIMARY KEY (`id`) ) ENGINE=InnoDB DEFAULT CHARSET=utf8; CREATE TABLE `cloud`.`port_profile` ( `id` bigint unsigned NOT NULL auto_increment COMMENT 'id', `uuid` varchar(40), `port_profile_name` varchar(255), `port_mode` varchar(10), `vsm_id` bigint unsigned NOT NULL, `trunk_low_vlan_id` int, `trunk_high_vlan_id` int, `access_vlan_id` int, `port_type` varchar(20) NOT NULL, `port_binding` varchar(20), PRIMARY KEY (`id`) ) ENGINE=InnoDB DEFAULT CHARSET=utf8; In case you created the db on or after May 14th from the 3.0.x branch, and the above tables already exist in the cloud database, you will need to alter some column names, and drop some. Please execute the following DMLs in this case: alter table virtual_supervisor_module drop column vcenterdcname; alter table virtual_supervisor_module drop column vcenteripaddr; alter table virtual_supervisor_module change column vsmDeviceState vsm_device_state varchar(20) NOT NULL; alter table virtual_supervisor_module change column ConfigState config_state varchar(20); alter table virtual_supervisor_module change column vsmDomainId vsm_domain_id bigint(20) unsigned; Regards, Vijay