Switching from using Baselines to Images (vLCM) may result in drift and report VIB/Component Removal Notifications
search cancel

Switching from using Baselines to Images (vLCM) may result in drift and report VIB/Component Removal Notifications

book

Article ID: 311882

calendar_today

Updated On:

Products

VMware Cloud Foundation VMware NSX VMware Live Recovery VMware vCenter Server VMware vCenter Server 8.0

Issue/Introduction

During transition of a Cluster from VMware Update Manager to vLCM Image, 'Check Image Compliance' task may result in drift, displaying VIB(s)/Component(s) Removal notifications.

Example:

  • VIB Removal Notification:
    "The following VIBs on the host are missing from the image hence will be removed from the host during remediation : <List of VIBs>. To prevent them from being removed, include appropriate components that are equivalent to these VIBs."

  • Component Removal Notification:
    "Components <List of Components> are removed in the image. They will be removed from the host during remediation. Add the Components to the image to retain them."

Environment

VMware Cloud Foundation 5.x

VMware Cloud Foundation 9.x

VMware vCenter Server 8.x

Cause

  • vSphere Lifecycle Manager (vLCM) enforces a strict "desired state" model.
  • If any VIB or Component currently installed on the host is not explicitly included in the newly defined vLCM Image, vLCM flags it for removal to ensure the host matches the exact desired state.

Resolution

  • Check if the VIB(s)/Component(s) displayed in the notification message match with VIB(s)/Component(s) listed in the Solution Removal Notification Table.

Solution Removal Notification Table:

Solutions

Type

VIB/Component Name

HA (High Availability)

VIB

vmware-fdm

NSX-T (version >= 3.1)

Component

nsx-lcp-bundle

Spherelet (WCP)

Component

VMware-Spherelet

vSphere Replication

VIB

vmware-hbr-agent

  • If Solution is enabled, corresponding solution's removal notifications can be ignored. After switching from Baselines to Images, the solution will now be set as part of the desired state. 
  • If the solution is not enabled, remediate the host after switching to vLCM images to remove the non-compliant VIB from the host.
  • If VIB(s)/component(s) list do not match with Solution Removal Notification table above, reach out to Broadcom Support for further assistance. 

Note: Solutions are the products integrated with Personality manager and enabled as a feature by the end user.
For example: HA, NSX-T

Additional Information

Note: For new "greenfield" installations of VCF 9.1, a warning can show up for switching to vLCM images even if there has been no upgrade, migration, or imports.  For this scenario, follow the following article to resolve: How to disable vCenter banner "Transition from vLCM Baselines to vLCM Images in a VCF environment should be performed via SDDC manager only."