Knowledge Base

The VMware Knowledge Base provides support solutions, error messages and troubleshooting guides
 
Search the VMware Knowledge Base (KB)   View by Article ID
 

Creating or editing a virtual machine Storage Policy to correct a missing Virtual SAN (VSAN) VASA provider fails (2075838)

Symptoms

  • 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.

Cause

This issue occurs if you are running vSphere 5.5 Update 1.

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.

Resolution

This is a known issue affecting VMware Virtual SAN 5.5.x. This issue is resolved in VMware vCenter 5.5 Update 1b, available at VMware Downloads. For more information, see the vCenter Server 5.5 Update 1b Release Notes.

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.
After completing the upgrade, recreate the VSAN to back up any critical information from the VSAN.

For more information on removing disks from Virtual SAN, see the Managing Disk Groups section in the vSphere Storage Guide.

Impact/Risks

Warning: Completing these actions may disrupt virtual machines running on the VSAN cluster. In this scenario, virtual machines must be moved to non-VSAN storage.

Tags

vsan, Virtual SAN, VASA

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.

Feedback

  • 3 Ratings

Did this article help you?
This article resolved my issue.
This article did not resolve my issue.
This article helped but additional information was required to resolve my issue.
What can we do to improve this information? (4000 or fewer characters)
  • 3 Ratings
Actions
KB: