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.
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.
> var/log/vmware/vcf/operationsmanager.log showing it is able to retrieve health for the cluster
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
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: CLUSTERNAME
java.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 with esxcli vsan health cluster list. Then this precheck can be safely ignored.