vLCM image Compliance Warning: vmware-fdm VIB missing from image

Products

• VMware vSphere ESXi

Issue/Introduction

• During a Cluster Image compliance check within the vSphere client, you encounter the following warning message:

The following VIBs on the host are missing from the image and will be removed from the host during remediation: vmware-fdm(8.0.x-<build_number>).



• The warning message is observed on vSphere 7.x and 8.x releases.
• Logs from /var/log/vmware/vmware-updatemgr/vum-server/vmware-vum-server.log show that despite successfully retrieving the vmware-fdm VIB and cluster image task, the installation found the VIB was already present.

YYYY-MM-DDTHH:MM info vmware-vum-server[1310188] [Originator@6876 sub=ImageManager::EnablementManager] [EnablementManager 1734] Identified vmware-fdm 8.0.x-<build_number> vib(s) belonging to vSphere FDM 8.0.x-<build_number> component present in the depot.
YYYY-MM-DDTHH:MM info vmware-vum-server[10349] [Originator@6876 sub=VumVapi::Lib::InstalledImages opID=20699c94-####-####-####-############] [Utils 318] Successfully retrieved InstalledImages task result from DB for cluster domain-c#: {
-->     "STRUCTURE": {
-->         "com.vmware.esx.settings.clusters.installed_images.installed_image_info": {
"id": "com.vmware.vcIntegrity.lifecycle.HostSeeding.OrphanVib",
-->   "default_message": "The following standalone VIB(s) are present on the host and will not be extracted: vmware-fdm(8.0.x-<build_number>)",
-->       "id": "com.vmware.vcIntegrity.lifecycle.HostSeeding.OrphanVib"


Environment

• VMware vSphere ESXi 7.x
• VMware vSphere ESXi 8.x

Cause

• The warning message can be caused by an orphaned VIB (vSphere Installation Bundle).
• The vmware-fdm VIB is installed automatically on an ESXi host when vSphere HA (High Availability) is enabled on a cluster, as `vmware-fdm` is not part of the base ESXi image and is pushed by vCenter only when HA is enabled. 
• The absence of the VIB in the image is not critical. When vSphere HA is enabled, it will automatically install the vmware-fdm VIB after the host exits maintenance mode, ensuring HA functionality is restored.

Resolution

1. Proceed with the remediation despite the warning.
2. After remediation is complete and the host exits maintenance mode, a reconfigure vSphere HA task should start installing FDM agents on the host.
3. If vSphere HA does not automatically reconfigure after the host is brought out of maintenance mode, you manually initiate the reconfiguration by right-clicking the host in the inventory and click on "Reconfigure for vSphere HA" from the dropdown list. 
4. If HA tasks are in a hung state and if tasks remain at 0% post remediation, perform a restart of the 'vpxd' service.