vSAN objects in "nonavailability-related-incompliance" state.

Products

• VMware vSAN

Issue/Introduction

The issue is noticed on the vSAN stretched cluster after renaming the fault domain.

You may experience the following on a vSAN stretched cluster.

• vSAN Skyline Health in vCenter will report an object health warning with the object in "nonavailability-related-incompliance".
• All host remediation tasks, like maintenance mode with ensured accessibility and adding or removing host tasks, will fail.
• Affected objects are configured with the 'locality' as NonPreferred in the vSAN Storage policy

Use the below command from the vSAN host command line to verify the health of the object.

#esxcli vsan debug object health summary get

 

Verify the details of the objects in "nonavailability-related-incompliance" using the below command.

#esxcli vsan debug object list --health=nonavailability-related-incompliance

The affected object will be having the locality set to 'NonPreferred'

 

Environment

VMware vSAN 7.x

VMware vSAN 8.x

Cause

This health check alert is triggered when an object’s storage policy compliance can’t be validated., This often happens due to stale metadata or incomplete compliance updates inside the vSAN control/management plane.

Resolution

Restart the vsanmgmt service on all the hosts in the vSAN cluster using the below command.

#/etc/init.d/vsanmgmtd restart

Additional Information

Impact/Risks

A vSAN object in nonavailability-related-incompliance status will not impact the production, as the objects will still be accessible.