vVols Datastore shows inaccessible in the vCenter after VI/Cluster creation.
search cancel

vVols Datastore shows inaccessible in the vCenter after VI/Cluster creation.

book

Article ID: 311981

calendar_today

Updated On:

Products

VMware Cloud Foundation

Issue/Introduction

This article helps to provide workaround/resolve the accessibility issue with the vVols Datastore.


Symptoms:

vVols Datastore shows inaccessible in the vCenter


Environment

Vmware Cloud Foundation 5.1

Cause

Missing certificates of the workload domain vCenter in the ESXi hosts cause this issue.

Resolution

Using/upgrading to VCF version 5100 (with vSphere 8.0U2) resolves the issue.


Workaround:

There are two ways by which missing trusted roots could be pushed to ESXi:

  • Using PowerShell and similar automation could be used with other SDK as well

$si = Get-View ServiceInstance
$certMgr = Get-View -Id $si.Content.CertificateManager
Get-VMHost | ForEach-Object -Process {
   $certMgr.CertMgrRefreshCACertificatesAndCRLs($_.Id)
}

  • By using UI on the VI Workload domain vCenter, as mentioned in below documentation link with "Refresh CA Certificates"

Renew or Refresh ESXi Certificates