I've just upgraded my 4 node vSAN cluster from 6.7 U3 to 7.0 U1 and my vSphere is keep saying that there is an error with vCLS vm's.
"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"
When im looking in to my VM and Templates folers there is an folder called vCLS but its empty.
I have tryied this: https://docs.vmware.com/en/VMware-vSphere/7.0/com.vmware.vsphere.resmgmt.doc/GUID-F98C3C93-875D-4570...
but still no luck.
Any soultions ?
First of all, make sure the upgrade from a vSAN point of view was successful. In other words, the vSAN Cluster/Datastore is health. You can do the VM provisioning check for instance to see if that works.
If you don't have the vCLS VMs being created and your vSAN is healthy and as such the cluster has a local vsan datastore, you can try to "disable/enable" vCLS, which will trigger the vCLS VM provisioning again.
I created a demo of how to do this here:
vSAN Skylline Health shows that vSAN is fully healthy.
I've also did Proactive Tests -> VM Creation, still all good
I've did exactly as you did in your Video, but still no luck, vCLS Folder is all time empty.
When the option is on True
Then in Cluster -> Monitor -> Events: Im getting this Error every 30 seconds "Cluster Agent VM is missing on cluster [Cluster Name] (vCLS)
When its on False
Nothing is happening.
It looks like that:
He first create a new folder vCLS then nothing is going on.
And it doesn't show any errors while it tries provisioning?
Please file a support request and do a log dump and include that. I don't know what is happening, but I have not seen this before, someone will need to look in to this.
Nope, there is not even a log that he would trie to provision anything.
Is this a lab or a production environment? And is the environment fully compliant with our HCL?
another report of a similar issue here by the way:
Would be great if you could also file an SR
Its production environment.
Host -> Updates -> Hardware Compatibility, shows few incomatibilities.
I did file the SR, number is: 20173050411