This issue occurs due to a VASA Provider registration mismatch. If the VASA Provider is onboarded to vCenter using an incorrect IP address (e.g., an individual node IP instead of the Cluster Management VIP) or incorrect credentials, it fails to properly communicate Capability Profiles to the vSphere Storage Policy SDK.
In some cases, the provider may show as registered in the OTV(Overlay Transport Virtualization) interface, but the security context or network path used for registration does not allow vCenter's Storage Management Service (SMS) to retrieve storage metadata.
To resolve this issue, unregister and re-register the VASA Provider using the correct Cluster Management IP and service account.