[
https://issues.apache.org/jira/browse/CLOUDSTACK-5098?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13844540#comment-13844540
]
Jessica Wang commented on CLOUDSTACK-5098:
------------------------------------------
Sateesh,
Actually, UI did once use listApis API to detect whether listVmwareDcs API
exists.
However, when listVmwareDcs API doesn’t exist (oss build), listAPIs API returns
error and leaves the error in log file which community members complaint
confusing.
They thought something wrong when they saw the word “error” in log file. And
most of them are using XenServer or KVM. They found it annoying and misleading
that log file caught error when every time they visited zone detail page.
That’s why I later changed UI to use listClusters to decide whether to call
listvmwareDcs API.
Because listClusters won’t return error when there is no clusters (i.e. won’t
leave an error in log file).
As opposed to listApis API that returns error when there is no such an API
(i.e. will leave an error in log file).
Jessica
> [UI] Zone view is showing "Add VMware Datacenter" button even though zone is
> already associated with a data center
> ------------------------------------------------------------------------------------------------------------------
>
> Key: CLOUDSTACK-5098
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5098
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: API
> Affects Versions: 4.2.1
> Reporter: Sailaja Mada
> Assignee: Jessica Wang
> Priority: Critical
> Fix For: 4.3.0
>
> Attachments:
> UI_changed_to_use_listClusters_instead_of_listApis_to_determine_whether_to_call_listVmwareDcs.PNG,
> apilog.log, management-server.log
>
>
> Steps:
> 1. Enable Nexus flag at the global level
> 2. Tried to configure the Adv zone with VMWARE hypervisor with out specifying
> Nexus vSwitch details while adding the cluster.
> With this Cluster addition failed . So i have cancelled the zone
> configuration.
> Now tried below steps:
> 1) Removed Pod and then tried to remove zone . It failed saying "The zone is
> not deletable because there are VMware datacenters associated with this zone.
> Remove VMware DC from this zone."
> 2) There is no Remove DC option , When i go to Zone details in the UI
> Observation:
> 1) Entries in vmware_data_center and vmware_data_center_zone_map are not
> cleaned up when there is a failure to add the cluster
> 2) So with this issue when i try to add the cluster , it is failing saying
> "This data center is already part of other Cloudstack Zone"
> So when there is a failure to add cluster for any reason , we should remove
> the addDC association in the DB aswell.
> I did delete the rows from vmware_data_center and vmware_data_center_zone_map
> , Then i was able to reuse the Datacenter
--
This message was sent by Atlassian JIRA
(v6.1.4#6159)
