Bug 1578581 - Power request errors with Gen10 servers
Summary: Power request errors with Gen10 servers
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: python-proliantutils
Version: unspecified
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: z2
: 13.0 (Queens)
Assignee: Bob Fournier
QA Contact: Shai Revivo
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-05-15 22:15 UTC by Adam Huffman
Modified: 2022-03-13 15:17 UTC (History)
12 users (show)

Fixed In Version: python-proliantutils-2.5.0-3.el7ost
Doc Type: Bug Fix
Doc Text:
Because of issues with multiple Sushy object creation on HP Gen10 servers, HPE Gen10 servers were not providing consistent response when accessing the system with id /redfish/v1/Systems/1. Instead of using session-based authentication, which is the default authentication method in Sushy, use basic authentication at the time of Sushy object creation. This results in no issues with power requests.
Clone Of:
Environment:
Last Closed: 2018-08-29 16:32:35 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Launchpad 1764395 0 None None None 2018-05-15 22:25:52 UTC
OpenStack gerrit 561191 0 'None' MERGED Fixes session issue for Gen10 servers 2021-02-17 12:29:35 UTC
Red Hat Issue Tracker OSP-13595 0 None None None 2022-03-13 15:17:21 UTC
Red Hat Product Errata RHBA-2018:2573 0 None None None 2018-08-29 16:33:24 UTC

Internal Links: 2077284

Description Adam Huffman 2018-05-15 22:15:59 UTC 
Description of problem:

I appear to be experiencing the problem outlined at:

https://bugs.launchpad.net/proliantutils/+bug/1764395

which means that node enrolment fails.

Version-Release number of selected component (if applicable):
Tested with TripleO Queens RDO packages (2.5.0).

How reproducible:


Steps to Reproduce:
1. openstack overcloud node import instackenv.json
2.
3.

Actual results:

Introspection fails.

Also worth noting that the nodes are put into maintenance mode because a Redfish call fails, even though I am using the 'ilo' driver, not 'redfish'.

Expected results:


Additional info:

During sync_power_state, max retries exceeded for node f92fdaa3-5f36-4000-b51a-dc46e9b2d1bd, node state None does not match expected state 'power on'. Updating DB state to 'None' Switching node to maintenance mode. Error: [iLO 10.150.0.10] The Redfish System "1" was not found. Error HTTP GET https://10.150.0.10/redfish/v1/Systems/1 returned code 401. iLO.0.10.ExtendedInfo: See @Message.ExtendedInfo for more information.
Comment 2 Clément Martin 2018-07-25 13:15:15 UTC 
We are also experiencing the same issue at a customer trying to deploy OSP13 using 'ilo' hardware type and Proliant DL360 Gen 10 servers.

I can confirm that the upstream patch fixes the issue.
Comment 3 Bob Fournier 2018-07-30 16:42:54 UTC 
Fix merged downstream.
Comment 13 Joanne O'Flynn 2018-08-13 11:19:07 UTC 
This bug is marked for inclusion in the errata but does not currently contain draft documentation text. To ensure the timely release of this advisory please provide draft documentation text for this bug as soon as possible.

If you do not think this bug requires errata documentation, set the requires_doc_text flag to "-".


To add draft documentation text:

* Select the documentation type from the "Doc Type" drop down field.

* A template will be provided in the "Doc Text" field based on the "Doc Type" value selected. Enter draft text in the "Doc Text" field.
Comment 15 errata-xmlrpc 2018-08-29 16:32:35 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2018:2573
Note You need to log in before you can comment on or make changes to this bug.