Resolving VCF LCM Failures and Inventory Drift Due to Out-of-Band Component Updates
search cancel

Resolving VCF LCM Failures and Inventory Drift Due to Out-of-Band Component Updates

book

Article ID: 453941

calendar_today

Updated On:

Products

VMware vSphere ESXi

Issue/Introduction

SDDC Manager Lifecycle Management (LCM) operations or Async Patch Tool (APT) processes fail in VCF environments.
Symptoms include "Bundle Not Found," "Manifest Mismatch," or LCM precheck failures citing version conflicts (e.g., component version newer than the BOM).
This is typically caused by manually patching ESXi or vCenter (Out-of-Band) rather than through SDDC Manager.

Environment

VMware Cloud Foundation (VCF) 5.x

Cause

"Inventory Drift" — when components (ESXi/vCenter) are manually updated, the actual component version diverges from the SDDC Manager database BOM.
This forces the LCM service into an unsupported state as it cannot orchestrate patching against a state it does not recognize.

Resolution

  1. Perform a full VCF BOM upgrade to the current supported target version (e.g., 5.2.4) via SDDC Manager UI.
  2. This process triggers an environment re-adoption/normalization of the component versions.
  3. If LCM prechecks persist, ensure the vCenter and ESXi versions align with the target BOM requirements before attempting the update bundle application.