Updating your vCenter to 8.0 Update 1, but ESXi hosts remain on an earlier version, vSphere Virtual Volumes datastores on such hosts might become inaccessible

Products

• VMware vCenter Server 8.0

Issue/Introduction

After updating vCenter to 8.0 Update 1, but before ESXi hosts are updated to 8.0U1, vSphere Virtual Volumes datastores on those hosts might become inaccessible.

Environment

vSphere 8.0 Update 1

vSphere APIs for Storage Awareness (VASA) version 5.0

Cause

Self-signed VASA provider certificates are no longer supported in vSphere 8.0 and the configuration option Config.HostAgent.ssl.keyStore.allowSelfSigned is set to false by default. When updating a vCenter instance to 8.0 Update 1 that introduces vSphere APIs for Storage Awareness (VASA) version 5.0, and ESXi hosts remain on an earlier vSphere and VASA version, hosts that use self-signed certificates might not be able to access vSphere Virtual Volumes datastores or cannot refresh the CA certificate.

Resolution

Update hosts to ESXi 8.0 Update 1 to fix the issue.

If a workaround is needed before patching hosts, follow the KB Seamless upgrade to VASA 5 for VMware Virtual Volume with backward compatibility.

Additional Information

Vsphere 8.0 update 1 release notes