VxRail: vCLS cannot deploy on vCenter after cluster rebooted

Summary: vSphere Cluster Services (vCLS) cannot deploy on vCenter after the cluster has been rebooted.

This article applies to This article does not apply to This article is not tied to any specific product. Not all product versions are identified in this article.
Check out other resources

Symptoms

vSphere Cluster Services (vCLS) cannot deploy on vCenter after the cluster has been rebooted.
  • Tried to set vCLS with retreat mode and disable it, but vCLS still cannot deploy on any ESXi host.
  • In the vCenter task list, can see vCenter continue to deploy vCLS and then destroy it.
/var/log/vmware/eam/eam.log: 
2024-03-28T03:08:14.942Z | ERROR | cluster-agent-0 | AuditedJob.java | 106 | JOB FAILED: [#1733615521] DeployVmJob(ClusterAgent(ID: 'Agent:cef3bd5a-3886-40a0-99eb-31b2b6bc677f:null')) com.vmware.eam.job.DeployVmJob$DeployVmJobFailure: Can't provision VM for ClusterAgent(ID: 'Agent:cef3bd5a-3886-40a0-99eb-31b2b6bc677f:null') due to lack of suitable datastore.
/var/log/vmware/vpxd/vpxd.log:  
2024-03-28T13:31:37.037+08:00 warning vpxd[12577] [Originator@6876 sub=VmProv opID=10847a9b] Unable to lookup ds for disk 



Cause

 DNS is unreachable and causes this issue.

Resolution

Check your DNS settings.
Ensure to use nslookup to resolve vCenter and all ESXi hosts FQDNs.
Article Properties
Article Number: 000226449
Article Type: Solution
Last Modified: 02 Jul 2024
Version:  1
Find answers to your questions from other Dell users
Support Services
Check if your device is covered by Support Services.