VSAN storage policy shows non compliant for all VMs after VSAN cluster move to new vCenter

Products

• VMware vSAN

Issue/Introduction

Symptoms 

- After vSAN cluster migration from one VC server to another VC server vSAN storage policy shows non compliant for all VMs 

- Migrated vSAN cluster is 2 node ROBO cluster

- After splitting a stretched cluster into 2 standard, and not correctly removing hosts from the original cluster.


Similar entries can be seen in sps.log on the vCenter appliance showing VMs as nonCompliant and inaccessible even though the VMs are not being affected and all data is also reported healthy in the UI and from the host level:

2025-08-13T12:40:21.034+02:00, mismatch = false, vsanDpHealthStatus = unknown}, vm-18771:2000=EntityComplianceResult{entity
= {key = vm-18771:2000, objectType = virtualDiskId}, profileId = {uniqueId = ########-####-####-####-############}, complianceStatus = nonCompliant, complianceTaskStatus = null, vsanHealthStatus = inaccessible, operationalStatus = {healthy = false, operationProgress = null, operationalEta = null, transitional = nul
l}, violatedPolicies = null

Environment

vSAN 8.0

Cause

Issue is caused by duplicate entries of VSAN cluster UUID for 2 or more VSAN clusters in VCDB 

 

 

.

Resolution

To resolve this issue please contact  Broadcom technical support