During transition of a Cluster from VUM to vLCM, Check Image Compliance may result in drift, displaying VIB(s)/Component(s) Removal notifications.
VMware NSX
VMware Cloud Foundation
During transition of a Cluster from VUM to vLCM desired state will not have Solution set, due to this Image Compliance Check may result in drift and reporting VIB removal warnings:
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.
vCenter Scan Result Notification UI:
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 |
|
vSphere Replication |
VIB |
vmware-hbr-agent |
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.
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 does not match with Solution Removal Notification table above, then the action needs to be assessed by the administrator.
Note: Solutions are the products integrated with Personality manager and enabled as a feature by the end user.
For example: HA, NSX-T