Bug 2077284

Summary: Power request errors with HPE Synergy servers
Product: Red Hat OpenStack Reporter: Siggy Sigwald <ssigwald>
Component: python-proliantutilsAssignee: OSP Team <rhos-maint>
Status: CLOSED NOTABUG QA Contact: nlevinki <nlevinki>
Severity: urgent Docs Contact:
Priority: unspecified    
Version: 16.2 (Train)CC: bfournie, eduen, hbrock, jkreger, jslagle, mburns
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2022-04-21 20:55:58 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Siggy Sigwald 2022-04-20 21:26:37 UTC 
Description of problem:

I found a bug[1] making reference to the same error:

The Redfish System "1" was not found. Error HTTP GET https://x.x.x.x/redfish/v1/Systems/1 returned code 401. iLO.0.10.ExtendedInfo: See @Message.ExtendedInfo for more information.

There's also an upstream bug[2]. Both seem to have been addressed already. I'll open a new BZ as it seems this is potentially the same error.

[1]https://bugzilla.redhat.com/show_bug.cgi?id=1578581
[2[https://bugs.launchpad.net/proliantutils/+bug/1764395
Version-Release number of selected component (if applicable):
Comment 1 Julia Kreger 2022-04-21 20:49:23 UTC 
The customer in our support case notes this is occurring when trying to utilize the `ilo` hardware type/drivers with a HPE Synergy system. The HPE "ilo" drivers[0] only support the Proliant series of hardware. Previously, I've discussed this fact with HPE's driver maintainers and they have noted that they would like to support the synergy and edgeline systems, but that they are developed by different product groups at HPE and thus the iLO does not know how to handle them appropriately.

My recommendation is to attempt to utilize the `redfish` hardware type instead of the `ilo` hardware type. This will cause Ironic to utilize redfish directly instead of attempting to utilize proliantutil's compatibility layer. This is what the upstream community recommends, and what is known to work with HPE Edgeline hardware.

If the customer has further issues with the redfish driver, we should likely work that as a distinct bug, but realistically this is more an issue of the proliant library doesn't understand the hardware and the hardware is not supported by the HPE maintained driver. As such, this BZ should likely be closed as either notabug or wontfix.

[0] https://docs.openstack.org/ironic/latest/admin/drivers/ilo.html