Loading...
Loading...
After upgrading to HPE OneView version 8.90 or 9.0, the firmware compliance may not function properly. The issue will only occur on servers or server profiles that had a firmware update performed while using an earlier version of OneView, such as, version 8.80, 8.70, or earlier.After OneView is upgraded, a firmware compliance check may fail even though the firmware update functioned correctly. In addition, the generic error message, "Firmware information is not available" may be displayed on the OneView User Interface.The issue occurs because OneView does not properly process firmware requests. The issue also impacts firmware compliance shown in REST, Curl, HPE OneView Powershell, and HPE OneView for VMware vCenter.When impacted, the profile may not show the firmware information and displays "firmware information is not available," however, it can automatically populate based on the last update and cannot reliably be used to identify the issue. The issue also impacts firmware compliance shown in REST, Curl, HPE OneView Powershell, and HPE OneView for VMware vCenter.The following example displays the missing firmware information on the HPE OneView User Interface:When impacted by this issue, the following URI "https://<OneView IP>/rest/server-hardware/<URI_OF_SERVER>" will work, however, the subsequent URI to firmware "https://<OneView IP>/rest/server-hardware/<URI_OF_SERVER>/firmware" will return an error (examples shown below).The following examples are found in HPE OneView Powershell, or REST:Example of the Error in HPE OneView Powershell:The first command is to get information on how the server functions:PS C:\Users\nairunai> Invoke-RestMethod -SkipCertificateCheck -Method GET -Headers $headers5 -Uri https://<domain name>/rest/server-hardware/34343338-3538-5250-4636-303630353132type : server-hardware-1name : 3-MXQxxxxxxx-TOP, bay 2state : ProfileErrorstateReason : NotApplicableassetTag :category : server-hardwarecreated : 09-Mar-23 8:27:00 PMdescription :eTag : 1721565466498formFactor : FullHeightlicensingIntent : NotApplicablelocationUri : /rest/enclosures/797740MXQxxxxxxxmemoryMb : 131072model : Synergy 620 Gen9modified : 21-Jul-24 12:37:46 PMmpDnsName : ILOPRF6060512.americas.hpqcorp.netmpFirmwareVersion : 2.76 Oct 31 2020mpIpAddress : fe80:0:0:0:9657:a5ff:fe67:a92ampModel : iLO4partNumber : 834485-B21portMap : @{deviceSlots=System.Object[]}position : 2powerLock : FalsepowerState : OffprocessorCoreCount : 24processorCount : 2processorSpeedMhz : 2100processorType : Genuine Intel(R) CPU 0000 @ 2.10GHzrefreshState : NotRefreshingromVersion : I40 v2.60 (05/23/2018)serialNumber : PXX6060512serverGroupUri : /rest/enclosure-groups/7554e345-3573-4af1-8515-f4f24a843650serverHardwareTypeUri : /rest/server-hardware-types/4E46491F-5CDE-4B2A-8EFA-EBAEB095AAB6serverProfileUri : /rest/server-profiles/129fda18-747f-4166-83d1-45daceeaae36shortModel : SY 620 Gen9signature : @{serverHwChecksum=1558378624; personalityChecksum=0}status : OKuri : /rest/server-hardware/34343338-3538-5250-4636-303630353132uuid : 34343338-3538-5250-4636-303630353132virtualSerialNumber : VCXHPPX00XvirtualUuid : 8bed5fd9-69fd-49b4-aaab-ff22e5d82566The second command is to get firmware information on the server (above) if it fails with the error below:PS C:\Users\nairunai> Invoke-RestMethod -SkipCertificateCheck -Method GET -Headers $headers5 -Uri https://<domain name>/rest/server-hardware/34343338-3538-5250-4636-303630353132/firmwareInvoke-RestMethod:{"errorSource": null,"data": {},"details": "The requested resource could not be found.","message": "Not Found","messageParameters": [],"nestedErrors": [],"errorCode": "GENERIC_HTTP_404","recommendedActions": ["Check the request URI, then resend the request.","Verify if the request requires an X-API-Version header."]}PS C:\Users\nairunai>Example of the Error in a OneView REST CallGET - https://<domain name>/rest/server-hardware/35393350-3133-584D-5133-323330395834/firmware{"errorSource":null,"data":{},"details":"The requested resource could not be found.","message":"Not Found","messageParameters":[],"nestedErrors":[],"errorCode":"GENERIC_HTTP_404","recommendedActions":["Check the request URI, then resend the request.","Verify if the request requires an X-API-Version header."]}This issue may impact HPE OneView for VMware vCenter component as well, if impacted please refer todocument a00142091, "HPE OneView for VMware vCenter (OV4VC) - OV4VC 11.5 or 11.6 May Fail to Remediate the Hosts After an HPE OneView 8.70 Update to Version 8.90 or 9.00."
HPE OneView 8.90 or 9.0 after a firmware update has been performed before the OneView update on any HPE Synergy or HPE ProLiant Gen10/Gen10 Plus/Gen11 Servers managed or monitored by the OneView appliance.
This issue is resolved by upgrading toHPE OneView 9.10.01.As a workaround when affected by this issue, select one of the following options:Use theHPE_Synergy_Composer2_Update_Z7550-97815.binfor managed or monitored servers.ORThe following options are also available:For Managed Mode Servers with an associated Server Profile:Re-apply the profile by selecting the "Reapply" option from the Actions menu.ORUse the REST call:PATCH https://{appl}/rest/server-profiles/{id}[{ "op" : "replace","path" : "/firmware/reapplyState","value" : "ApplyPending"}]For Monitored Mode Server Hardwares: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 the BaselineUri, FirmwareInstallType, and InstallationPolicy with the appropriate values that were previously used.After performing the workaround, depending on SP or SH, the firmware compliance calculation will work as expected.Document VersionRelease DateDetails3October 29, 2024Updated the Resolution with the HPE_Synergy_Composer2_Update_Z7550-97815.bin workaround information.2October 09, 2024Updated the Resolution with the permanent fix.1July 31, 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.