Error: Host image does not match image set for cluster due to Dell HSM TPM firmware failure
search cancel

Error: Host image does not match image set for cluster due to Dell HSM TPM firmware failure

book

Article ID: 451467

calendar_today

Updated On:

Products

VMware vSphere ESXi

Issue/Introduction

This article addresses a vSphere Lifecycle Manager (vLCM) remediation failure where hosts report as non-compliant due to a third-party Hardware Support Manager (HSM) firmware mismatch, specifically involving Dell OpenManage.

  • vLCM remediation fails with the error: A general system error occurred: After host '####' remediation completed, compliance check reported host as 'non-compliant'. The image on the host does not match the image set for the cluster.
  • Full image comparison shows a TPM version mismatch (e.g., host running 7.2.3.1 while bundle requires 7.2.4.1).
  • vCenter reports a stale reference to a deleted baseline and cannot find the object.

Environment

  • VMware vSphere ESXi 7.x / 8.x
  • VMware vCenter Server 7.x / 8.x
  • Dell OpenManage Enterprise Integration for VMware vCenter (OMEVV) / Hardware Support Manager (HSM)

Cause

The initial failure is caused by the Dell HSM failing to apply a third-party TPM firmware package during the vLCM workflow. The subsequent retrieval error occurs because vCenter retains a stale metadata reference to the baseline in the Dell OpenManage plugin after deletion.

Resolution

To resolve the compliance and stale reference issues, perform the following:

  1. Remove HSM Bundle from Image:

    • Navigate to the cluster Updates tab.
    • Select Image > Edit.
    • Click the trash can icon next to the Firmware and Drivers Addon (HSM bundle).
    • Save the image and rerun compliance. This allows native ESXi components to update successfully.
  2. Clear Stale Baseline Reference:

    • Open the Dell OpenManage console.
    • Navigate to the baseline profile impacted.
    • Assign a different repository profile to the baseline.
    • Switch the repository profile back to the original profile.
    • This forces a synchronization refresh between OpenManage and vCenter, clearing the stale reference.

For critical security patches, ensure you are running the latest supported versions. Fixed in release ESXi #### and higher. See Download Broadcom Products and Software to download the latest release.

Additional Information

For proactive monitoring, subscribe to this article at How to subscribe to Broadcom KB articles.