VASA provider registration fails with Certificate error in vSphere client.

Products

• VMware vCenter Server

Issue/Introduction

VVOL datastore shows inaccessible in vCenter UI and changing the Storage Array IP. 

Checking the vasa provider on the host shows " Status: Offline: AuthenticationError [Vasa Provider Certificate not trusted (self-signed certificate in certificate chain)]" 

Checking the Storage provider in vCenter does not show the provider registered. 

When trying to register the vasa provider fails with Certiticate error in vSphere client. 

SMS logs in vCenter shows below errors while creating the virtual host in version.xml file 

com.vmware.vim.binding.sms.fault.ProviderRegistrationFault: CreateVirtualHost call failed against provider with url https://examplearray.com:port/vasa/version.xmlcom.vmware.vim.vasa._5_0.StorageFault: StorageFault

 

Environment

VMware vSphere 7.x 

VMware vSphere 8.x 

VMware vSphere 9.x 

Cause

After certificate validation during the provider registration, a virtualhost with vCenter IP and guid will be created and updated in version.xml file in the vasa provider server. If the version.xml file is not found or corrupt then the registration will fail with StorageFault exception thrown by the VASA provider. 

Resolution

Verify the version.xml file is accessible by following either opening the vasa provider URL in a browser or run wget from vCenter SSH. Note: The necessary port requirement for vasa provider connectivity needs to allowed.

You should see something similar to below 

<vasa-provider>
<supported-versions>
<version id="3" serviceLocation="/vasa/services/vasaService?version=2"/>
<version id="4" serviceLocation="/vasa/services/vasaService?version=3"/>
<version id="5" serviceLocation="/vasa/services/vasaService?version=4"/>
<version id="7" serviceLocation="/vasa/services/vasaService/v5"/>
</supported-versions>
</vasa-provider>

If there is no output similar to above, involve the array vendor and verify the version.xml. 

In a specific case, it was observed that the symlink to the version.xml file was broken in the vasa provider and after restoring the symlink the registration was successfull.