vSphere 8.1 - VASA5 - Certificate Details Mis-match upon VASA Provider Registration

Products

• VMware vCenter Server 8.0
• VMware SDDC Manager

Issue/Introduction

VASA 5.0 for VVOL VASA providers was introduced in 80U1 product release.

With VASA 5.0, a VVOL VASA Provider supports multiVC (register same VP to multiple vCenters) through VirtualHost. When such VASA Provider is registered to SMS/vCenter, SMS only communicates with the specific VirtualHost corresponds to vCenter post bootstrapping stage during register. Certificate data shown for such VASA Provider is incorrect, i-e, instead of VirtualHost certificate, certificate of default endpoint is displayed.

Environment

vCenter 8.0 u1 and above 

VCF 5.0 and above 

 

Cause

VirtualHost certificate is not fetched and updated in the DB, instead certificate of default endpoint which is used to register VASA Provider is used is set as VirtualHost/VP certificate in the SPS DB.

Resolution

Currently there is no workaround. Product fix is required and Broadcom Engineering is currently working on this.

Additional Information

Fix is in progress and will be available in the next major release and mostly VCF 9.0.