When running prechecks in 5.2 VCF, there is a failing precheck, with the name "Cluster vSAN Health Unknown" in SDDC Manager, despite the vSAN health showing healthy in vCenter.
DescriptionReport failures in fetching cluster vSAN health statusHealth statusERRORError description vSAN Health status fetch failed for cluster <Cluster-name> with domain name: <Domain-name-Here>IMPACTHigh: NSX vSAN Stretch Cluster Prechecks may not have been run for this cluster thereby masking any underlying issues that may cause upgrades to failRemediationRe-run the failed prechecks. If the issue persists, please check operation manager logs.
Observed in 5.2 & 5.2.1 VCF environments
This appears to be an issue with the operationsmanager service where it fails to parse the vSAN health despite the health being accessible to SDDC Manager.
We seem to be able to retrieve the health status for the cluster:# less var/log/vmware/vcf/operationsmanager.log
DEBUG [vcf_om,676417c5ee6e1f3f252248388b30bfff,59d5] [c.v.v.b.n.v.NsxtStretchClusterCompositeValidator,precheck-validation4] Successfully fetched vsansummary for cluster: CLUSTERNAME
The same log shows, that is unable to fetch/parse the vSAN health# less var/log/vmware/vcf/operationsmanager.log 2024-11-13T06:16:54.854+0000 ERROR [vcf_om,0000000000000000,0000] [c.v.v.b.n.v.NsxtStretchClusterCompositeValidator,ForkJoinPool.commonPool-worker-1204] Error fetching vsanClusterHealthSummary for cluster: CLUSTERNAMEjava.lang.IllegalArgumentException: com.vmware.vim.binding.vmodl.query.PropertyCollector referenced from a method is not visible from class loader: 'app'
If the vSAN health in vCenter is all green, and if the vSAN health, has been validated from the ESXi command line, via example from below, then this precheck can be safely ignored.# esxcli vsan health cluster listhttps://techdocs.broadcom.com/us/en/vmware-cis/vsan/vsan/7-0/vsan-monitoring/handling-failures-and-troubleshooting-virtual-san/using-esxcli-commands-with-vsan.html