vCenter vCLS VMs missing after upgrade from vSphere 6.5..

  • Home
  • vCenter vCLS VMs missing after upgrade from vSphere 6.5..

vSphere Cluster Services (vCLS) is a new feature in vSphere 7.0 Update 1. This feature ensures cluster services such as vSphere DRS and vSphere HA are all available to maintain the resources and health of the workloads running in the clusters independent of the vCenter Server instance availability.

In vSphere 7.0 Update 1, VMware has released a platform/framework to facilitate them to run independently of the vCenter Server instance availability. In this release, vCenter Server is still required for running cluster services such as vSphere DRS, vSphere HA etc.

Reference: Click here.

After I had upgraded my lab from vSphere 6.5 to 7, I noticed these new fangled vCLS VMs were nowhere to be found. I tried the following which didn’t seem to help.
1. Create new cluster and migrate hosts.
2. The config.vcls.clusters trick. See reference link above.
3. Disable/enable both HA and DRS on the cluster.

After review of my vCenter eam.log file from “/var/log/vmware/eam”, I noticed similar errors found in conjunction to borked vCLS..
com.vmware.eam.job.DeployVmJob$DeployVmJobFailure: Can’t provision VM for ClusterAgent(ID: ‘Agent:xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx:null’) due to lack of suitable datastore.

What finally fixed it for me was a combination of using the Lookup Service Doctor (lsdoctor) and the fixsts.sh script.

lsdoctor: Click here. I ran both –trustfix and –rebuild.
fixsts: Click here.

Before my upgrade I was running vCenter 6.7 and ESXi 6.5. I found a ton of posts online about using lsdoctor, but I didn’t find the fixsts script right away. Hopefully this saves you some time. In fact, the VMware article on this doesn’t even provide the fixsts link.
Reference: Click here.

Regards,
Adam Tyler

Leave a Reply