Remediation of cluster failedHealth Check for '<cluster name>' failedHealth Check fails to retrieve data about service 'Workload Management Platform' on '<cluster id>'. Verify that the service 'Workload Management Platform' is running and try again. /var/log/vmware/wcp/wcpsvc.log on vCenter Server:Failed to read VCSA proxy settings from file '/etc/sysconfig/proxy' with error: open /etc/sysconfig/proxy: too many open fileUnable to get the list of clusters: Post "http://localhost:1080/sdk": dial tcp: lookup localhost: device or resource busyUnable to collect information for cluster agencies: Post "http://localhost:1080/sdk": dial tcp: lookup localhost: device or resource busyvCenter Server
vSphere Supervisor
The wcp service on vCenter Server is not in a healthy state.
To workaround the issue, restart wcp service on vCenter Server with below command:
service-control --restart wcpAlternatively, the service can also be restarted in vCenter Server Appliance Management Interface(VAMI) by selecting "Workload Control Place" service and click "RESTART".
Further checks should be made in the environment to understand the cause of the wcp service failure.
If there is a Supervisor cluster in the environment, its status and underlying system components should be checked for any issues which may be contributing to the wcp service's failure.