Remediation of hosts from lifecycle manager fails for "UPDATE_PRE_CHECK" with error "HPE GreenLake for Compute Ops Management"

Products

• VMware vCenter Server

Issue/Introduction

vCenter version=8.0.2, build=23504390

When remediating hosts from lifecycle manager, below error is seen:

Environment

VMware vCenter 8.x

Cause

a. The error message from logs indicate that the host was failed remediation pre-check because it does not match the associated server group in HPE Compute Ops Management.

b. Compute Ops Management simplifies and unifies operations across the server lifecycle, for the whole environment, no matter where your compute infrastructure lives. It provides a consistent, secure cloud experience that scales elastically and unifies compute management.

c. The plug-in uses the Compute Ops Management firmware update capability therefore, each host in a vCenter cluster must be on-boarded to Compute Ops Management before performing any vLCM operations on that cluster.

 

vmware-vum-server.log

vmware-vum-server-40.log:2024-09-11T05:56:51.177Z info vmware-vum-server[09967] [Originator@6876 sub=RemediateClusterTask] [Task, 511] Task:com.vmware.vcIntegrity.lifecycle.RemediateClusterTask ID:<cluster-id>. Remediating host ID: host-11, Name: <hostname> - hosts queue size = 1 - host group queue size 1 - retry candidate queue size = 0
vmware-vum-server-40.log:2024-09-11T05:56:51.179Z info vmware-vum-server[09967] [Originator@6876 sub=RemediateClusterTask] [Task, 511] Task:com.vmware.vcIntegrity.lifecycle.RemediateClusterTask ID:<cluster-id>. Remediating host ID: host-11, Name: <hostname>
vmware-vum-server-40.log:2024-09-11T05:57:00.699Z info vmware-vum-server[12160] [Originator@6876 sub=Telemetry] [TelemetryManager 423] Sending telemetry data: {"@type":"pman_error_report","taskId":"39636c87-1cb0-414a-b797-f2a6d4c35555|2171a314-0aed-4872-bed3-f6d91e9ee482","entityId":"<entity-id>|host-11","parentTaskId":"39636c87-1cb0-414a-b797-f2a6d4c35555|<cluster-id>","errorMessageId":"FROM_DOWNSTREAM: The hosts in the vCenter cluster are not matching with the associated Server Group in HPE GreenLake for Compute Ops Management.","errorMessage":"","errorTime":"2024-09-11T05:57:00.699015Z"}
vmware-vum-server-40.log:2024-09-11T05:57:00.703Z error vmware-vum-server[09967] [Originator@6876 sub=RemediateClusterTask] [Task, 511] Task:com.vmware.vcIntegrity.lifecycle.RemediateClusterTask ID:<cluster-id>. Skipping host(<hostname>) due to HW pre-check failure
vmware-vum-server-40.log:2024-09-11T05:57:00.703Z info vmware-vum-server[12160] [Originator@6876 sub=Telemetry] [TelemetryManager 423] Sending telemetry data: {"@type":"pman_error_report","taskId":"39636c87-1cb0-414a-b797-f2a6d4c35555|52e9cbd2-fe99-7e70-ef7b-b9d2aca313ba","entityId":"<entity-id>|domain-c8","parentTaskId":"","errorMessageId":"com.vmware.vcIntegrity.lifecycle.RemediateClusterTask.HwUpdate.Unsuccessful","errorMessage":"Hardware update action: 'UPDATE_PRE_CHECK' for host '<hostname>' 'FAILED' on HSM 'HPE GreenLake for Compute Ops Management'.","errorTime":"2024-09-11T05:57:00.703577Z"}
vmware-vum-server-40.log:2024-09-11T05:57:00.708Z info vmware-vum-server[09967] [Originator@6876 sub=RemediateClusterTask] [Task, 511] Task:com.vmware.vcIntegrity.lifecycle.RemediateClusterTask ID:<cluster-id>. RemediateClusterTask - after scheduling host(host-11 - <hostname>) for retrying remediation. retry count(0) - max retry count (2)

Resolution

The issue is not due to vCenter/ESXi so we recommend engaging Hardware vendor (HPE) to understand about Compute Ops management hardware pre-check failure. For more details please refer to HPE's documentation.