Unable to refresh live checks for resource ####-####-####-#### in new local inventory"/var/log/vmware/vcf/domainmanager/domainmanager.log
YYYY-MM-DDTHH:MIN:SEC DEBUG [vcf_dm,####,####,a362] [c.v.v.q.i.p.vim.VimResultConverter,vcf-ds-294] Received a response from 'vCenter FQDN'YYYY-MM-DDTHH:MIN:SEC WARN [vcf_dm,####,####,a362] [c.v.v.q.i.p.vim.VimResultConverter,vcf-ds-294] vimResultSet items is nullYYYY-MM-DDTHH:MIN:SEC DEBUG [vcf_dm,####,####,a362] [c.v.e.s.c.s.utils.VcResourceNameUtil,http-nio-127.0.0.1-7200-exec-9] returned values getClusterNames {####-####-####-####=null}
YYYY-MM-DDTHH:MIN:SEC DEBUG [vcf_dm,####,####] [c.v.v.c.service.ResourceCacheService,dm-exec-20] SddcManagerController ####-####-####-#### is in ACTIVE status.YYYY-MM-DDTHH:MIN:SEC INFO [vcf_dm,####,####] [c.v.v.c.service.ResourceCacheService,dm-exec-20] Loading isConfigRealized checks for changed resources and refresh failed checks...YYYY-MM-DDTHH:MIN:SEC INFO [vcf_dm,####,####] [c.v.v.c.service.ResourceCacheService,dm-exec-20] Refreshing live checks for HOST with id ####-####-####-####YYYY-MM-DDTHH:MIN:SEC INFO [vcf_dm,####,####] [c.v.v.c.service.ResourceCacheService,ForkJoinPool.commonPool-worker-219] Refreshing live checks for CLUSTER with id ####-####-####-####YYYY-MM-DDTHH:MIN:SEC INFO [vcf_dm,####,####] [c.v.v.c.service.ResourceCacheService,ForkJoinPool.commonPool-worker-220] Refreshing live checks for CLUSTER with id ####-####-####-####YYYY-MM-DDTHH:MIN:SEC INFO [vcf_dm,####,####] [c.v.v.c.service.ResourceCacheService,dm-exec-20] Refreshing live checks for HOST with id ####-####-####-####YYYY-MM-DDTHH:MIN:SEC INFO [vcf_dm,####,####] [c.v.v.c.service.ResourceCacheService,dm-exec-20] Refreshing live checks for HOST with id ####-####-####-####YYYY-MM-DDTHH:MIN:SEC INFO [vcf_dm,####,####] [c.v.v.c.service.ResourceCacheService,ForkJoinPool.commonPool-worker-219] Refreshing live checks for HOST with id ####-####-####-####YYYY-MM-DDTHH:MIN:SEC INFO [vcf_dm,####,####] [c.v.v.c.service.ResourceCacheService,ForkJoinPool.commonPool-worker-219] Refreshing live checks for HOST with id ####-####-####-####YYYY-MM-DDTHH:MIN:SEC INFO [vcf_dm,####,####] [c.v.v.c.service.ResourceCacheService,ForkJoinPool.commonPool-worker-220] Refreshing live checks for HOST with id ####-####-####-####YYYY-MM-DDTHH:MIN:SEC INFO [vcf_dm,####,####] [c.v.v.c.service.ResourceCacheService,ForkJoinPool.commonPool-worker-219] Refreshing live checks for HOST with id ####-####-####-####YYYY-MM-DDTHH:MIN:SEC INFO [vcf_dm,####,####] [c.v.v.c.service.ResourceCacheService,ForkJoinPool.commonPool-worker-220] Refreshing live checks for HOST with id ####-####-####-####YYYY-MM-DDTHH:MIN:SEC INFO [vcf_dm,####,####] [c.v.v.c.service.ResourceCacheService,ForkJoinPool.commonPool-worker-219] Refreshing live checks for HOST with id ####-####-####-####YYYY-MM-DDTHH:MIN:SEC INFO [vcf_dm,####,####] [c.v.v.c.service.ResourceCacheService,ForkJoinPool.commonPool-worker-220] Refreshing live checks for CLUSTER with id ####-####-####-####YYYY-MM-DDTHH:MIN:SEC ERROR [vcf_dm,####,####] [c.v.v.c.service.ResourceCacheService,dm-exec-20] Unable to refresh live checks for resource ####-####-####-#### in new local inventoryjava.util.NoSuchElementException: null at java.base/java.util.ArrayList$Itr.next(ArrayList.java:970) at java.base/java.util.Collections.min(Collections.java:601) at com.vmware.vcf.configreconciler.service.ResourceCacheService.isEsxVersionChanged(ResourceCacheService.java:1073)
VCF 9.x
SDDC Manager is unable to list ESX host inventory information for the said cluster in a WLD domain. Performing out-of-band changes to vCenter server inventory, such as decommissioning ESX host from vCenter server instance rather than SDDC Manager, shall lead to this behavior. SDDC Manager shall hold stale entries of ESX host or cluster names in its database.
This requires validation of stale ESX hosts and SDDC database edits. Database edits are destructive in nature, raise a Broadcom Support Case to seek further assistance.
Note: It shall be helpful if following details are included in the Support Case, so that the issue can be validated and reference stale entries.