VASA API version does not automatically refresh after upgrade to vCenter Server 8.0

Products

• VMware vCenter Protect 8.x and 9.x
• VMware vCenter Server 8.0

Issue/Introduction

vCenter Server 8.0 supports VASA API version 4.0. However, after you upgrade your vCenter Server system to version 8.0, the VASA API version might not automatically change to 4.0. 

Environment

8.0 Upgrade 3F and Below

Cause

You see the issue in 2 cases:

1. If a VASA provider that supports VASA API version 4.0 is registered with a previous version of VMware vCenter, the VASA API version remains unchanged after you upgrade to VMware vCenter 8.0. For example, if you upgrade a VMware vCenter system of version 7.x with a registered VASA provider that supports both VASA API versions 3.5 and 4.0, the VASA API version does not automatically change to 4.0, even though the VASA provider supports VASA API version 4.0. After the upgrade, when you navigate to 

   vCenter Server > Configure > Storage Providers and expand the General tab of the registered VASA provider, you still see VASA API version 3.5.
2. If you register a VASA provider that supports VASA API version 3.5 with a VMware vCenter 8.0 system and upgrade the VASA API version to 4.0, even after the upgrade, you still see VASA API version 3.5.

Resolution

Workaround:

Unregistering and re-registering the VASA Provider on vCenter will re-establish new session with the VASA version latest supported by VASA Provider and switch to 4.0.

This issue is resolved in 8.0 Update 3G

Additional Information

VMware vCenter 8.0 Update 3g Release Notes