Firmware compliance details are missing from a vSphere Lifecycle Manager image compliance report for an ESXi standalone host

Products

• VMware vCenter Server

Issue/Introduction

This KB article informs the user about the bug present in the vLCM FW compliance result UI page for Standalone hosts and Guides the users to work around this issue until the fix is provided in future releases.

Symptoms:
Firmware compliance details might be missing from a vSphere Lifecycle Manager image compliance report for an ESXi standalone host in two cases:

1. Run a compliance report against a vSphere Lifecycle Managed stand-alone host from vSphere Client next navigate away before or after the compliance report gets generated.
2. Trigger a page refresh after the image compliance report is generated.

In such cases, even though the firmware package is available in the Desired State, the firmware compliance section remains empty when you revisit or refresh the vSphere Client browsing session.

If you use GET image compliance API, firmware compliance details will be missing from the response.

Environment

VMware vCenter Server 8.0.1
VMware vCenter Server 8.0.x

Cause

This issue is caused due to a vLCM back-end bug.

Resolution

Workaround:

Follow the below steps:

1. Invoke the image compliance scan for vSphere Lifecycle Managed stand-alone host through vSphere client and do not navigate away or refresh the browser.
2. For API, use the Check image compliance API for fetching the firmware details as opposed to GET image compliance.

This issue is resolved in this release-VMware vCenter 8.0 Update 3g - https://techdocs.broadcom.com/us/en/vmware-cis/vsphere/vsphere/8-0/release-notes/vcenter-server-update-and-patch-release-notes/vsphere-vcenter-server-80u3g-release-notes.html

 

Additional Information

Firmware compliance details are missing from a vSphere Lifecycle Manager image compliance report for an ESXi standalone host

Firmware compliance details might be missing from a vSphere Lifecycle Manager image compliance report for an ESXi standalone host in two cases:

• You run a compliance report against a vSphere Lifecycle Manager image in the vSphere Client and then navigate away.
• You trigger a page refresh.

In such cases, even when you have the firmware package available in the Desired State, the firmware compliance section remains empty when you revisit or refresh the vSphere Client browsing session.

If you use API, firmware compliance details are missing from the response.

This issue is resolved in this release-VMware vCenter 8.0 Update 3g