Red Hat Bugzilla – Bug 1578581
Power request errors with Gen10 servers
Last modified: 2018-08-29 12:33:24 EDT
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.
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.
Fix merged downstream.
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.
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