vSAN Skyline health reports an inaccessible object for a PVC with Read Write Many access mode using vSAN File Services

Products

• VMware vSphere Kubernetes Service
• VMware vCenter Server

Issue/Introduction

vSAN Skyline Health reports an Inaccessible object.

While using vSAN File Services  under Skyline Health  - Virtual Objects  container volumes are shown as "Inaccessible" However there is a duplicate PVC which is accessible. 

The PVC uses "ReadWriteMany" Access mode leveraging vSAN File Services.

 

Environment

VMware vCenter Server 8.0

VMware vSAN 8.0 

Cause

The object is flagged as inaccessible as it has no corresponding backing vSAN object.

There will be an inaccessible object showing in virtual object list in the UI. However, while creating file share based CNS volume, it is working fine. The issue is the mapping between CNS file volume and the vSAN object missed and it failed to build the map between FCD and CNS file volume. So system thinks there is no vSAN object for the FCD and reported the false inaccessible object.

In the Virtual Center logs, we can see messages similar to the following

/var/log/vmwae/vsan-health/vsanvcmgmtd.log

210018:2024-04-17T06:39:43.626Z ERROR vsan-mgmt[08899] [VsanSpaceReportSystemImpl::populateFcdBackingObjects opID=WorkQueue-1183146b-adda] Get error usedB for file:51a4cafd-9cd4-4785-9d55-1cad7411b012 with -1
210019:2024-04-17T06:39:43.627Z ERROR vsan-mgmt[08899] [VsanSpaceReportSystemImpl::populateFcdBackingObjects opID=WorkQueue-1183146b-adda] Get error usedB for file:e3713b16-544e-44fa-87b0-4748a9c74144 with -1

Resolution

This is a cosmetic issue with no impact to the accessibility of the PVC.

The PVC showing inaccessible issue from CNS fixed in 8.0 U3.

The health warnings improvement will be in ESXi 9.0