Host remediation failure during firmware patching due to incorrect baseline type

Products

• VMware vCenter Server

Issue/Introduction

Host remediation fails during an attempt patch firmware (e.g., from version 4.3.2 to 4.3.5) utilizing VMware vSphere Lifecycle Manager (vLCM).

The following error message is returned in the vSphere Client during the remediation attempt:
VMware vSphere Lifecycle Manager had an unknown error. Check the events and log files for details.

The vmware-vum-server logs confirm that a baseline compliance scan fails because the system attempts to process an Upgrade baseline instead of a Patch baseline:

 yyyy-mm-ddTss:ss:ss.973+08:00 info vmware-vum-server[######] [Originator@6879 sub=Activation.trace] [activationValidator 1131] Invoke done: integrity.ComplianceStatusManager.queryEntityComplianceStatus
--> Result:
--> (integrity.ComplianceStatusManager.EntityBaselinesComplianceSummary) {
-->    summary = (integrity.ComplianceStatusManager.EntityComplianceCountsSummary) {
-->       notCompliantEntities = 1,
-->       inCompatibleEntities = 0,
-->       unknownEntities = 0,
-->       compliantEntities = 0
-->    },
-->    baselinesComplianceStatus = (integrity.ComplianceStatusManager.EntityBaselinesCompliance) [
-->       (integrity.ComplianceStatusManager.EntityBaselinesCompliance) {
-->          entity = 'vim.HostSystem:<HOSTNAME>',
-->          status = "NotCompliant",
-->          baselineId = (int) [
-->             15
-->          ],
-->          baselineType = "Patch",
-->          lastScanTime = "2026-04-23T07:58:07.963Z",
-->          toolsUpgradeOnPowerCycle = false
-->       },
-->       (integrity.ComplianceStatusManager.EntityBaselinesCompliance) {
-->          entity = 'vim.HostSystem:<HOSTNAME>',
-->          status = "Unknown",
-->          baselineId = (int) [
-->             13
-->          ],
-->          baselineType = "Upgrade",
-->          lastScanTime = <unset>,
-->          toolsUpgradeOnPowerCycle = false

Environment

VMware vCenter Server 8.x

VMware ESXi 8.x

Cause

• An incorrect baseline type (Upgrade Baseline) is attached to the host for a vendor firmware operation.
• Upgrade baselines are strictly intended for major version upgrades (e.g., ESXi 7.x to 8.x or ESXi 8.x to 9.x).
• Firmware and driver updates require the use of a patch or extension baseline, specifically utilizing an OEM Add-On.

Resolution

 

• Download the appropriate OEM Add-On from the Broadcom Support Portal.

• Import the OEM Add-On into vCenter Server.

• Create a new baseline using the imported add-on. Ensure the baseline type is set correctly (Patch/Extension).

• Use the newly created baseline to remediate and patch the host.

 

Additional Information

Recommendation: Consider migrating to an image-based cluster to manage the entire cluster using a single desired image. This simplifies the inclusion and management of vendor add-ons compared to baseline-based lifecycle management.

For more information, please review the following documentation on how to Remediate ESXi Hosts Against a Single Baseline or Multiple Baselines.