Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1791392

Summary: Redfish PM driver not working with Supermicro
Product: Red Hat OpenStack Reporter: phalmos
Component: python-sushyAssignee: Ilya Etingof <ietingof>
Status: CLOSED ERRATA QA Contact: Arik Chernetsky <achernet>
Severity: medium Docs Contact:
Priority: medium    
Version: 16.0 (Train)CC: achernet, athomas, bfournie, dbecker, dsneddon, ietingof, jkreger, mburns, morazi, rpittau
Target Milestone: betaKeywords: Triaged
Target Release: 16.1 (Train on RHEL 8.2)   
Hardware: x86_64   
OS: Unspecified   
Whiteboard:
Fixed In Version: python-sushy-2.0.3-0.20200522054330.0241cd9.el8ost Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-07-29 07:50:33 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 phalmos 2020-01-15 17:34:56 UTC
Description of problem:
When trying to import and introspect Supermicro using Redfish PM driver it fails when attempting to get power state with error "Error: The attribute Registry is missing from the resource /redfish/v1/Registries/Base.1.0.0"

Version-Release number of selected component (if applicable):
RHOSP 16 beta

How reproducible:


Steps to Reproduce:
1. install undercloud
2. create json file with nodes
3. attempt import using 'openstack overcloud node import --introspect --provide ~/instackenv.json'

Actual results:
import fails with: Exception registering nodes: {'result': 'Failure caused by error in tasks: send_message\n\n  send_message [task_ex_id=592d66bf-8dbd-421f-a929-cba8d12e94df] -> Workflow failed due to message status. Status:FAILED Message:({\'result\': \'Node bc14499a-ab5a-44fc-b9ce-e78b2c09cc1f did not reach state "manageable", the state is "enroll", error: Failed to get power state for node bc14499a-ab5a-44fc-b9ce-e78b2c09cc1f. Error: The attribute Registry is missing from the resource /redfish/v1/Registries/Base.1.0.0\'}, {\'result\': \'Node 29468faa-4eec-4a13-93c1-7f4e9e76ee43 did not reach state "manageable", the state is "enroll", error: Failed to get power state for node 29468faa-4eec-4a13-93c1-7f4e9e76ee43. Error: The attribute Registry is missing from the resource /redfish/v1/Registries/Base.1.0.0\'}, {}, {}, {}, {}, {}, {})\n    [wf_ex_id=2950e39e-dc6a-4e10-a8de-faa1a143cbc6, idx=0]: Workflow failed due to message status. Status:FAILED Message:({\'result\': \'Node bc14499a-ab5a-44fc-b9ce-e78b2c09cc1f did not reach state "manageable", the state is "enroll", error: Failed to get power state for node bc14499a-ab5a-44fc-b9ce-e78b2c09cc1f. Error: The attribute Registry is missing from
the resource /redfish/v1/Registries/Base.1.0.0\'}, {\'result\': \'Node 29468faa-4eec-4a13-93c1-7f4e9e76ee43 did not reach state "manageable", the state is "enroll", error: Failed to get power state for node 29468faa-4eec-4a13-93c1-7f4e9e76ee43. Error: The attribute Registry is missing from the resource /redfish/v1/Registries/Base.1.0.0\'}, {}, {}, {}, {}, {}, {})\n', 'status': 'FAILED', 'message': [{'result': 'Node bc14499a-ab5a-44fc-b9ce-e78b2c09cc1f did not reach state
"manageable", the state is "enroll", error: Failed to get power state for node bc14499a-ab5a-44fc-b9ce-e78b2c09cc1f. Error: The attribute Registry is missing from the resource /redfish/v1/Registries/Base.1.0.0'}, {'result': 'Node 29468faa-4eec-4a13-93c1-7f4e9e76ee43 did not reach state "manageable", the state is "enroll", error: Failed to get power state for node 29468faa-4eec-4a13-93c1-7f4e9e76ee43. Error: The attribute Registry is missing from the resource /redfish/v1/Registries/Base.1.0.0'}

Expected results:
node gets imported

Additional info:
These servers worked correctly in OSP13 using the redfish PM driver.  The correct path that does exist is "/redfish/v1/Registries/Base.v1_4_0"

Comment 1 Dmitry Tantsur 2020-01-17 14:32:47 UTC
Discussed this and a similar issue upstream. We need to become more relaxed around the registries handling, apparently.

Comment 2 Ilya Etingof 2020-01-29 21:06:37 UTC
Update and clarification: linked upstream patch proposes a way to ignore schema violation problems as they raise. However, said patch might not solve this problem. I am hopeful that once we settle the approach to working around issues like this one, pushing a patch ignoring missing Registry (the essence of this BZ) will be quick and easy.

Comment 3 Julia Kreger 2020-02-21 16:16:50 UTC
Patches have merged, 2.0.2 was released upstream with them for stable/train, so if we want to update what we are shipping for stable/train, this issue should then be resolved.

Comment 4 Bob Fournier 2020-02-28 16:28:51 UTC
Ilya will make final change for this, we'll need to make sure everything is backported to stable/train to get picked up for OSP-16.

Comment 5 Ilya Etingof 2020-03-09 14:05:54 UTC
@phalmos: if you could try the linked patch against your system, that would be awesome!

Thanks!

Comment 6 Bob Fournier 2020-03-09 14:10:21 UTC
Moving to ON_DEV until patch merges (and is backport to Train merges).

Comment 11 errata-xmlrpc 2020-07-29 07:50:33 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-2020:3148