The VMware Knowledge Base provides support solutions, error messages and troubleshooting guides
Creating or editing a virtual machine Storage Policy to correct a missing Virtual SAN (VSAN) VASA provider fails (2075838)
- The Virtual SAN VASA provider is not listed in VMware Virtual SAN 5.5.
- You cannot create a Storage Policy due to the unlisted Virtual SAN VASA.
- You cannot edit existing Storage Policies on the virtual machine.
The Resync VSAN Providers option on the Storage Providers user interface (UI) is not operational in vSphere 5.5 Update 1. It cannot fix the discrepancy between the hosts added to VSAN clusters and VPs shown on the Storage Provides UI. If you click Resync VSAN Providers, or restart the vmware-sps process, VPs corresponding to hosts that were added to VMware vCenter Server using their DNS names disappears from the Storage Providers UI.
To work around this issue if you cannot upgrade, you must add hosts to VSAN by IP address.
Depending on whether the host was added to vCenter Server using DNS name or IP address:
Warning: Completing these actions may disrupt virtual machines running on the VSAN cluster. In this case, virtual machines must be moved to non-VSAN storage.
- If the relevant host was added to vCenter Server using its IP address, move the host out of the VSAN cluster and move it back in again.
- If the relevant host was added to vCenter Server using its DNS name, place the host into Maintenance mode, remove the host from vCenter Server inventory, and add the host back with its IP address.
For more information on removing disks from Virtual SAN, see the Managing Disk Groups section in the vSphere Storage Guide.
Request a Product Feature
To request a new product feature or to provide feedback on a VMware product, please visit the Request a Product Feature page.