Firmware and Drivers Add-on Remediation Fails for vSAN Clusters Using vLCM
Article ID: 427349
Updated On:
Products
Issue/Introduction
Firmware and Drivers Add-on remediation fails when initiated from vCenter Server for vSAN clusters using vSphere Lifecycle Manager (vLCM).
The remediation task reports the following errors:
Remediation of cluster failed
<host> Skipping remediation for this host
Skipping host because its compliance information is unavailable. Please check the host status.
- vCenter [Scan Task] Unable to find the baseline profile with the provided version
vmware-vum-server.log on vCenter will show below entries
Path: /var/log/vmware/vmware-updatemgr/vum-server/vmware-vum-server.logerror vmware-vum-server[2074364] [Originator@6876 sub=HostFirmwareInfo] [HostFirmwareInfo 236] Error for host-xxxx is: Error:
--> com.vmware.vapi.std.errors.error
--> Messages:
--> com.vmware.vcIntegrity.lifecycle.HwSupport.Hsm.ListHostInventory.Failed<Failed to list host inventory from hsm HPE OneView for VMware vCenter and endpoint https://<vCenter FQDN>:3512/rest/ovm/vlcm.>
error vmware-vum-server[2042036] [Originator@6876 sub=Hsl::ScanManager opID=#########-#######-#####-####-###########] [ScanManager 213]
Unable to convert hsm com.hpe.ov4vc.vlcmhsm's taskinfo with id: ######-####-####-####-########## into Scan taskinfo. Error - Error:
--> com.vmware.vapi.std.errors.error
--> Messages:
--> vapi.data.error.getfield.unknown<GetField unknown field: fwCompliance>
info vmware-vum-server[2042036] [Originator@6876 sub=Hsl::Util::ScanUtil opID=#########-#######-#####-####-###########] [ScanUtil 610] hsmHostComplianceMap is Empty
warning vmware-vum-server[2042036] [Originator@6876 sub=Hsl::Util::ScanUtil opID=#########-#######-#####-####-###########] [ScanUtil 181
] Failed to convert hsmHostComplianceMap to hostHsmHspComplianceMap and hostHsmRemediationImpactMap
hsm.log shows compliance checks are unknown:
Path: /var/log/vmware/vmware-updatemgr/vum-server/hsm-service.log
Retrieved information of task ######-####-####-####-##########: {"action":"SCAN","complianceScanMap":{"host-xxxx":{"messages":["Error: Compliance results unavailable for host host-xxxx. Reason: Unable to find host in HPE OV."]}},"description":"Scan a set of hosts for firmware compliance and report remediation impact.","estimatedTimeRemaining":0,"hosts":["host-xxxx"],"id":"bc59f941-05b4-4a80-a56d-3ca07093664b","messages":["Compliance Scan of ['host-xxxx'] was successful"],"operationStatusCode":200,"progress":100,"startTime":"2026-01-21 08:33:38.046490","status":"SUCCEEDED"}
{"firmwareVersion": "1.04", "systemComponent": {"description": "Universal Backplane Manager", "id": "######-####-####-####-##########", "name": "8 SFF 24G x4NVMe/SAS UBM6 BC BP", "type": "EXTERNAL"}}], "hosts": ["host-xxxx"], "id": "5079a743-58ab-4849-aca2-9a5386b63a40", "messages": ["Error occured during inventory of host-xxxx"], "operationStatusCode": 500, "progress": 100, "startTime": "yyyy-mm-dd hh:mm:ss", "status": "FAILED"}', 'error': None}
HsmService:[MainThread]hsmService:745 [INFO] HSM Service is initialized
HsmService:[Dummy-65]hsmService:436 [ERROR] get_host_inventory failed with InternalServerError
HsmService:[Dummy-65]hsmService:540 [ERROR] ['Failed to start inventory for host-xxxx']
HsmService:[Dummy-65]hsmService:547 [INFO] Got http response status code: 500
HsmService:[Dummy-65]hsmService:558 [ERROR] Error code: 500
HsmService:[Dummy-65]hsmService:561 [ERROR] Transient error: None
HsmService:[Dummy-65]hsmService:797 [INFO] Hsm service result: {'output': 'null', 'error': {'errorCode': 500, 'command': ('hosts', 'get'), 'input': '{"requestContext": null, "optArguments": {"host_id": "host-xxxx", "package": "Service pack for HPE ProLiant Gen11", "version": "SPP-2025.07.00.00.803"}}', 'args': {'status': 500, 'message': ['Failed to start inventory for host-17022'], 'isTransient': 'null'}}}
Environment
- VMware vCenter Server 7.x
VMware vCenter Server 8.x - VMware vSphere ESXi 7.x
VMware vSphere ESXi 8.x - VMware vSAN 7.x
VMware vSAN 8.x
Hardware Support Manager Integration such as
- HPE OneView for VMware vCenter
Cause
The issue occurs due to a failure in hardware compatibility validation between vLCM and the hardware vendor’s Hardware Support Manager (HSM) plugin.
Specifically:
The HSM plugin fails to return host inventory and firmware compliance data to vLCM.
As compliance information is unavailable, vLCM skips the affected hosts and fails remediation.
Resolution
Contact the hardware vendor responsible for the HSM plugin (for example, HPE for HPE OneView).
Verify the following with the vendor:
HSM plugin health and service status
Version compatibility between vCenter, ESXi, vLCM, and the HSM plugin
Connectivity between vCenter Server and the HSM endpoint
Host visibility and inventory status within the vendor’s hardware management platform
Supported Hardware Support Managers are listed in the Broadcom Compatibility Guide:
https://compatibilityguide.broadcom.com/search?program=hsm&persona=live&column=partnerName&order=asc
Additional Information
https://knowledge.broadcom.com/external/article/388422/esxi-upgrade-precheck-error-error-on-fet.html
Feedback
