[
https://issues.apache.org/jira/browse/CLOUDSTACK-4198?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sateesh Chodapuneedi resolved CLOUDSTACK-4198.
----------------------------------------------
Resolution: Not A Problem
This is by design if the setup has only 1 cloudstack zone. Please re-open if
there exists 2 cloudstack zones.
Because the query "select * from cluster" is showing 2 clusters which are from
different VMware datacenters, its evident that cloudstack zone is a legacy
zone. In case of legacy zone we populate the table "legacy_zones" and would not
populate vmware_datacenter & vmware_datacenter_zone_map. These 2 tables contain
only those datacenters that are associated with cloudstack zone by following
the constraint of 1 DC per zone. It seems the setup has 2 different DCs per
single zone. In that case the zone would continue work as it was working
earlier as a legacy zone. For detailed design, please go through FS for the
feature here,
https://cwiki.apache.org/confluence/display/CLOUDSTACK/Mapping+model+for+CloudStack+zone+and+Vmware+datacenter
> 3.0.6 to ASF 4.2 Upgrade: "vmware_data_center" and
> "vmware_date_center_zone_map" tables are not populated with the vmware data
> centers information
> --------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: CLOUDSTACK-4198
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4198
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: VMware
> Affects Versions: 4.2.0
> Reporter: Chandan Purushothama
> Assignee: Sateesh Chodapuneedi
> Priority: Critical
> Fix For: 4.2.0
>
>
> After Upgrade, I expected the VMWare Clusters information to be populated in
> the two tables: "vmware_data_center" and "vmware_date_center_zone_map". I
> observed empty tables
> mysql> select * from vmware_data_center;
> Empty set (0.00 sec)
> mysql> select * from vmware_data_center_zone_map;
> Empty set (0.04 sec)
> mysql> select * from cluster;
> +----+------------------------------+--------------------------------------+--------------------------------------+--------+----------------+-----------------+-----------------+------------------+---------------+---------+-------+---------+-------------+--------------+
> | id | name | uuid |
> guid | pod_id | data_center_id |
> hypervisor_type | cluster_type | allocation_state | managed_state |
> removed | owner | created | lastUpdated | engine_state |
> +----+------------------------------+--------------------------------------+--------------------------------------+--------+----------------+-----------------+-----------------+------------------+---------------+---------+-------+---------+-------------+--------------+
> | 1 | 10.223.52.61/VMDC/clus1 | 2bc52adc-0345-426d-b4dc-b10bb26b475c |
> c4ca4238-a0b9-3382-8dcc-509a6f75849b | 1 | 1 | VMware
> | ExternalManaged | Enabled | Managed | NULL | NULL |
> NULL | NULL | Disabled |
> | 2 | 10.223.52.61/OTHERVMDC/clus2 | e80bff91-598e-4d4e-8951-205311a979d4 |
> c81e728d-9d4c-3f63-af06-7f89cc14862c | 2 | 1 | VMware
> | ExternalManaged | Enabled | Managed | NULL | NULL |
> NULL | NULL | Disabled |
> +----+------------------------------+--------------------------------------+--------------------------------------+--------+----------------+-----------------+-----------------+------------------+---------------+---------+-------+---------+-------------+--------------+
> 2 rows in set (0.00 sec)
> mysql>
--
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
