Loading...
Loading...
HPE OneView for VMware vCenter 11.5 or 11.6 may fail to remediate the HPE Synergy and HPE ProLiant server hosts managed or monitored by HPE OneView after HPE OneView 8.70 has been upgraded to version 8.90 or 9.00.When this occurs, the hosts in a cluster will show their status as "Host status is unknown" during the precheck in HPE OneView for HPE VMware vCenter 11.5 or 11.6. The message will occur because the remediation is skipped when OneView attempts to pre-check for VMware vCenter 11.5 or 11.6. The upgrade from OneView 8.70 to 8.90 causes the information to be shown as unavailable, even though the system is functioning correctly.Expected output from REST call.GET https://{appl}/rest/server-hardware/{uuid}/firmwareTo confirm whether the issue is caused by the OneView upgrade, make an OV4VC appliance support dump to check for the cause, for example:OV4VC Comprehensive logs:C:\collection_062428861Z\< ov4vc FQDN>\log\var\log\ov4vc\ovm\ovm.log:2024-06-18 14:31:47,189 11010 140666881435392 ERROR vlcm.actions.host_management_action scan_hosts_for_compliance_task Exception for ['host-33427'] in compliance_scan_task_info: ('An unexpected error occurred.', {'errorCode': 'UNEXPECTED_EXCEPTION', 'message': 'An unexpected error occurred.', 'details': 'An unexpected and unhandled runtime exception occurred.', 'messageParameters': [], 'recommendedActions': ['Please contact your authorized support representative and provide them with a support dump.'], 'errorSource': None, 'nestedErrors': [], 'data': {}})vCenter logs:<vcenter log>\var\log\vmware\vmware-updatemgr\vum-server\ vmware-vum-server.logFrom vCenter SSH session:/var/log/vmware/vmware-updatemgr/vum-server/vmware-vum-server.log:2024-05-15T02:04:15.335Z info vmware-vum-server[40445] [Originator@6876 sub=ServiceProvider] [EmbeddedPyServiceProvider 1779] HSM Task Info JSON String: {"action": "SCAN", "description": "Scan a set of hosts for firmware compliance and report remediation impact.", "estimatedTimeRemaining": 0, "hosts": ["host-3041", "host-3223", "host-3827", "host-3969", "host-4003"], "id": "8371ef65-cb66-48ae-babd-bad6500f6c11", "messages": ["Error occurred during compliance scan task of ['host-3041', 'host-3223', 'host-3827', 'host-3969', 'host-4003']."], "operationStatusCode": 500, "progress": 100, "startTime": "2024-05-15 02:03:54.370300", "status": "FAILED"}2024-05-15T02:04:15.335Z info vmware-vum-server[40445] [Originator@6876 sub=Hsl::TaskManager] [TaskManager 274] Task: 8371ef65-cb66-48ae-babd-bad6500f6c11 on hsm: com.hpe.ov4vc.vlcmhsm is FAILED2024-05-15T02:04:15.335Z error vmware-vum-server[40445] [Originator@6876 sub=VumVapi::Lib::Utils] [Utils 263] Failed to perform type conversion.2024-05-15T02:04:15.335Z error vmware-vum-server[40445] [Originator@6876 sub=VumVapi::Lib::Utils] [Utils 265] Could not convert native types: GetField unknown field: complianceScanMap2024-05-15T02:04:15.335Z error vmware-vum-server[40445] [Originator@6876 sub=Hsl::ScanManager] [ScanManager 214] Unable to convert hsm com.hpe.ov4vc.vlcmhsm's taskinfo with id: 8371ef65-cb66-48ae-babd-bad6500f6c11 into Scan taskinfo. Error - Error:--> com.vmware.vapi.std.errors.error--> Messages:--> vapi.data.error.getfield.unknown<GetField unknown field: complianceScanMap>-->This issue is caused by OneView and additional details about this issue are documented indocument a00142114, "HPE OneView - Firmware Compliance May Not Function Properly After Upgrading to OneView Version 8.90 or 9.0."
HPE OneView for VMware vCenter (OV4VC) and HPE OneView 8.90 or 9.0 that manages or monitors HPE Synergy or HPE ProLiant Gen10/Gen10 Plus/Gen11 Servers.Note: This will also affect vSphere Lifecycle Management (vLCM), vCenter Server Profiles, vCenter Server Update Planner and vSphere Lifecycle Manager (vLCM).
This issue is resolved by upgrading toHPE OneView 9.10.01.Select one of the following workarounds:Use this workaroundHPE_Synergy_Composer2_Update_Z7550-97815.binfor managed or monitored servers.ORThe following workarounds are also available:ForManaged Mode Serverwith an associated Server Profile:Re-apply the profile by selecting the "Reapply" option from the Actions menu.ORUse the provided REST call:PATCH https://{appl}/rest/server-profiles/{id}"path" : "/firmware/reapplyState","value" : "ApplyPending"}]ForMonitored Mode ServerHardwares:Select "Update firmware" from the Actions menu and apply the previously used Service Pack for ProLiant (SPP).ORUse the following REST call:PATCH https://{appl}/rest/server-hardware/{id}/firmware/settings[ { "op": "replace","value": {"baselineUri": "/rest/firmware-drivers//{fwBaselineId}","firmwareInstallType": "FirmwareOnly","installationPolicy": "LowerThanBaseline"}}]Note: Replace BaselineUri, FirmwareInstallType, and InstallationPolicy with the appropriate settings used previously after taking steps for the Managed or Monitored Mode Servers:Document VersionRelease DateDetails3October 29, 2024Updated the Resolution with HPE_Synergy_Firmware_Compliance_Z7550-97817.bin workaround information.2October 09, 2024Updated the Resolution with the permanent fix.1July 30, 2024Original Document Release.
Operating Systems Affected:Not Applicable
Click on a version to see all relevant bugs
Hewlett Packard Enterprise Integration
Learn more about where this data comes from
Bug Scrub Advisor
Streamline upgrades with automated vendor bug scrubs
BugZero Enterprise
Wish you caught this bug sooner? Get proactive today.