While setting up Horizon 6 in my home lab today, I needed to spin up a new virtual machine. As usual, I deployed it via my template and when the wizard reached the select storage options, things started to get – funny. I wanted to place the virtual machine on the vsanDatastore, but when I selected he Storage Policy that already was defined, the vsanDatastore were incompatible. It was stating that the Datastore does not match the given VM profile.
The first thing that came to my mind was that the profile driven storage service may have stopped as this is the service responsible for the storage policies. When I checked the vCenter Service Health, all was nice and green.
So the next thing was to check the storage policy itself. I went through the options and found it very interesting that under the rule-set it was able to identify my VSAN storage. I interpreted it as VASA (vSphere API for Storage Awereness) is functioning.
But under the matching ressources, there storage policy could not identify any matching VSAN datastore!
I checked the status of the storage providers – all was normal here.
I did check status of the disks/diskgroups and the network just to be sure. I would have seen other errors though if some of theese components were failing, so I checked anyways just to rule it out.
So I came to the conclusion that VSAN is running fine, but the storage policies were not able to identify the vsanDatastore for some reason. As I mentioned earlier. the vSphere Profile-Driven Storage service are responsible for the storage policies, so I checked the service on the vCenter server itself, and though it was running I restarted it.
That did it. Now my storage policy were able to identify a matching storage.
And I could finally continue my journey to the Horizon.