DRS functionality is impacted due to unhealthy state of vSphere Cluster Services (vCLS) on pure IPv6 deployments

Products

• VMware vCenter Server 8.0

Issue/Introduction

The following errors are observed:

• A warning in the vSphere client:
  
  vSphere DRS functionality was impacted due to unhealthy state vSphere Cluster Services caused by the unavailability of vSphere Cluster Service VMs. vSphere Cluster Service VMs are required to maintain the health of vSphere DRS


• Under the cluster summary page, the cluster services panel has:
  
  "Cluster Service health" as "Unhealthy" 
  and
  "Cluster Service type" set to "Embedded vCLS"
  
  
• The following error is present in /var/run/log/infravisor.log on ESXi:
  
  2024-04-09T15:07:14Z No(5) infravisor[525493]: time="2024-04-09T15:07:14.080958Z" level=error msg="Failed to get resource from spec vcls.yaml: failed to decode pod from /etc/vmware/infravisor/manifests/vcls.yaml: ValidatePodCreate failed: [spec.nodeName: Invalid value: \"<Node_name>\": a lowercase RFC 1123 subdomain must consist of lower case alphanumeric characters, '-' or '.', and must start and end with an alphanumeric character (e.g. 'example.com', regex used for validation is\
'[a-z0-9]([-a-z0-9]*[a-z0-9])?(\\.[a-z0-9]([-a-z0-9]*[a-z0-9])?)*')]"

The following conditions must be met for this issue to occur:

1. DRS is enabled on a cluster
2. A cluster has at least 1 pure IPv6 host with ESXi 8.0 U3
3. FQDNs for the 8.0 U3 host is not configured correctly (or set to local host)
4. There are no powered-on external vCLS VMs in the cluster

Environment

This issue requires VMware vCenter Server 8.0 U3 and ESXi 8.0 U3.

Cause

As part of the vCLS deployment workflow, the configured FQDN of the host (or IPv4 address) is used as an identifier for the host. This workflow fails on pure IPv6 deployments if the FQDNs are not configured explicitly and correctly. One of the services in the workflow (infravisor) is unable to validate using an IPv6 address as the host identifier, thereby failing to create vCLS VMs. 

Resolution

This issue will be resolved in a future release. 

Follow one of the two options to workaround the issue:

1. Configure a valid FQDN for the hosts and restart the infravisor service.
2. Configure the hosts to also have an IPv4 address and restart the infravisor service. 

Note: The infravisor service can be restarted by running: /etc/init.d/infravisor restart