vVOL Datastore is inaccessible - Error message in sps logs "Host name could not be verified!"

Products

• VMware vCenter Server

Issue/Introduction

Symptoms:

• vVOL datastore is seen as inaccessible in vCenter Ui and/or Host Client, i.e., the vVOL datastore may be seen as accessible in vCenter but a few hosts may have issues accessing the vVOL datastores.
• VASA Provider is shown as Offline on vCenter.
• Some VMs may still be working without issues.
• vCenter may have been upgraded or a new vCenter may have been registered to the VASA Provider.
• You see in sps.log messages similar to:

 <vCenter Server's /var/log/vmware/vmware-sps/sps.log>

2024-06-26T12:45:17.747Z [pool-9-thread-4] ERROR opId=sps-Main-119359-972 com.vmware.vim.sms.util.CustomSslSocketFactory - CompositeTrustManager could not validate certificate:

2024-06-26T12:45:17.748Z [pool-9-thread-4] ERROR opId=sps-Main-119359-972 com.vmware.vim.sms.util.CustomHostNameVerifier - [verify] Hostname verification failed for host: 10.xx.xx.xxx
javax.net.ssl.SSLPeerUnverifiedException: peer not authenticated
    at sun.security.ssl.SSLSessionImpl.getPeerCertificates(SSLSessionImpl.java:440)
    
2024-06-26T12:45:17.748Z [pool-9-thread-4] ERROR opId=sps-Main-119359-972 com.vmware.vim.sms.provider.vasa.alarm.AlarmDispatcher - Error occurred while polling alarms for provider: https://10.xx.xx.xxx:8084/version.xml
com.vmware.vim.sms.fault.VasaServiceException: org.apache.axis2.AxisFault: Host name could not be verified!

• You see "sync error" when listing the VASA provider on ESXi CLI:

[root@localhost:~] esxcli storage vvol vasaprovider list
example-name
   VP Name: example-name
   URL: https://10.xx.xx.xxx:8084/version.xml
   Status: syncError
   Arrays:
         Array Id: com.exampleID:2dxxxxxd-6xxx-4xxx-bxxx-axx8xxcxx3xx
         Is Active: true
         Priority: 200

Environment

vCenter 7.0.x

vCenter 8.0.x

Resolution

To correct this, the Storage Provider has to be re-registered in the vCenter Server.

 

vCenter 7.0.x

• Be sure to have the Storage Provider authentication information.
• In the Storage Providers tab, remove the offline VASA provider from vCenter and add it again using the Storage Provider's credentials. (NOTE: The FQDN in the URL must match the subject of the storage endpoint certificate, or you will continue to get sync errors.)

 

vCenter 8.0.x

• In the Storage Providers tab, find the offline VASA provider.
• Click on the 3 dots on the left of the VASA provider's name.
• Click on Re-authenticate vCenter Server and when the wizard appears on the screen, fill it with the Storage Provider's credentials and click Save.