VMware vSphere Lifecycle Manager baseline scans fail when scanning vCenter environment from the Datacenter level

Products

• VMware vCenter Server

Issue/Introduction

An error is experienced when scanning the vCenter environment for Lifecycle Manager Baseline compliance at the Datacenter level. 
Error: VMware vSphere Lifecycle Manger had an unknown error. Check the log files for details. 

The vmware-updatemgr may crash and create a core dump within the /storage/core/ directory. The dump will appear with a name similar to core.updatemgr-worke.#####

Within /var/log/vmware/vmware-updatemgr/vum-server/vmware-vum-server.log, the scan hangs or errors attempting to scan a ESXi host identified by IP:
YYYY-MM-DDTHH:MM:SS.000Z info vmware-vum-server[#######] [Originator@#### sub=SingleHostUpgradeScanTask.SingleHostUpgradeScanTask{12}] [singleHostUpgradeScanTask 366] Scanning host ###.###.###.### against upgrade VMware ESXi 8.0.3 Update 3 (profile name = )

The host indicated in the log above will be a HCX Mobility Appliance presented in the vCenter inventory as a ESXi host and not an actual ESXi host. 

Environment

vCenter 8.0u3

Cause

The vCenter Update Manger is attempting to scan the compliance of the HCX Mobility Agents to the ESXi baselines present in the vCenter and failing. 

Resolution

As a workaround, the environment can be scanned at the cluster level. The HCX Mobility Agents will only be deployed external to ESXi host clusters. 

To resolve the issue, reset the VMware Update Manager database of the vCenter appliance and rescan the environment. See: Resetting the VMware Update Manager Database

If the issue persists after resetting the VUM DB, please open a case with Broadcom support.