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

Products

• VMware Cloud Foundation

Issue/Introduction

Symptoms:

While switching from using Baselines to using Images, Check Image Compliance may result in drift, displaying VIB(s)/Component(s) Removal notifications.

Cause

While switching from using Baselines to using Images, desired state will not have solution⁽¹⁾ set, Because of this Check Image Compliance may result in drift and report VIB/Component Removal notifications.

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. If this is seen while switching from using Baselines to using Images, please refer to KB 90188.

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. If this is seen while switching from using Baselines to using Images, please refer to KB 90188. 

vCenter Scan Result Notification UI:

 

Resolution

Please check if the VIB(s)/Component(s) displayed in the notification message matches with VIB(s)/Component(s) listed in the Solution Removal Notification Table and take Recommended Action described below.

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

If Solution is enabled, corresponding solution's removal notifications can be ignored and will disappear after switching from Baselines to Images as the solution will now be set as part of the desired state. 

Note: If VIB(s)/component(s) list does not match with Solution Removal Notification table, then the action needs to be assessed by Admin.

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

 

Workaround:

No workaround available.