Well, one student created his own cluster, apparently checked the box for VSAN cluster in the process, added his host to it, then realized he was supposed to be in the "shared" DRS Host Cluster.
He deleted the cluster he had created, re-added his host to vCenter and when he tried to move his host into the DRS Cluster, he got the following error:
It turns out there was a VSAN datastore created with no disks in it and, his host still had an affiliation with the VSAN Cluster that no longer existed.
To resolve the problem we did the following:
- From Storage inventory view in vCenter, verify a VSAN datastore still exists.
- If it does, Putty into the ESXi host or access it via its ESXi Shell & execute the command:
esxcli vsan cluster get
- If results appear, proceed to the solution ...
- From previous command line (SSH or ESXi Shell) to the affected host, execute the following command:
esxcli vsan cluster leave
- Now add the host to the existing Host Cluster...