Orphan vib" messages and handling in vLCM

Products

• VMware vSphere ESXi

Issue/Introduction

This article will help in clarifying why they see these warning messages and guide them on the next steps.

Symptoms:

A warning message is displayed in vSphere Lifecycle Manager client after a compliance check, cluster upgrade or transition pre-check stating that "The following VIBs on the host are missing from the image and will be removed from the host during remediation: <VIB names>".
Examples of warning messages:
 

1. Messages displayed after Compliance check: 
2. Messages displayed in pre-check details:
3. Messages displayed in transition from baseline-managed to single-image managed cluster:
4. Message displayed for a host that has fdm component but currently not part of HA-enabled single-image managed cluster: 

 

 

 

 

 

 

 

Environment

VMware vSphere 7.0.x
VMware vSphere ESXi 8.0.x

Cause

The issue occurs when vSphere Lifecycle Manager detects old VIBs in the ESXi host which are not included in the target image. 

Resolution

Note:  This message is for informational purpose only and does not block remediation operation.

This is an intentional behavior in vSphere Lifecycle Manager (single image-based workflows) from vSphere 7.0, targeted to removal of old/unused content from ESXi host. When the cluster upgrade is initiated, the old/unused content mentioned in the message will be automatically removed from the hosts by vSphere Lifecycle Manager.

If one or more VIBs mentioned in the warning need to be present on the host - they need to be added to the target image as a component. For more information on how to add a component to the target image, please refer to vSphere Lifecycle Manager product documentation (https://docs.vmware.com/en/VMware-vSphere/8.0/vsphere-lifecycle-manager/GUID-CBCAC2B6-7C30-4103-89C5-C53FEEA59D0A.html). If a component with the respective VIB(s) cannot be found in the depot, please contact VIB vendor for the latest support information.

Workaround:

Currently there is no workaround, as this is an intended behavior. Please refer to  "Resolution" section for steps to resolve the issue".