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

Bug 1649894

Summary:	Cannot introspect Power 9 Witherspoon system
Product:	Red Hat OpenStack	Reporter:	Ann Marie Rubin <arubin>
Component:	openstack-ironic	Assignee:	Tony Breeds <tonyb>
Status:	CLOSED ERRATA	QA Contact:	Barry Donahue <bdonahue>
Severity:	urgent	Docs Contact:
Priority:	urgent
Version:	14.0 (Rocky)	CC:	bfournie, dgilmore, mariel, mburns, rgrange, tonyb, tvardema, wsun
Target Milestone:	rc	Keywords:	Triaged
Target Release:	14.0 (Rocky)
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	openstack-ironic-11.1.1-0.20181012152842.el7ost	Doc Type:	Bug Fix
Doc Text:	Some commands from the OpenStack Bare Metal service (Ironic) to BMCs with IPMI hardware failed due to hardware driver errors. This prevented bare metal nodes from booting. This fix adds the `ipmi_disable_boot_timeout` hardware driver option, which prevents Ironic from sending these commands to IPMI hardware.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-01-11 11:54:45 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:
Bug Depends On:
Bug Blocks:	1649892

Description Ann Marie Rubin 2018-11-14 17:56:25 UTC

Description of problem: Power 9 Witherspoon systems do not work on RHOSP 14 because of this bug: https://storyboard.openstack.org/#!/story/2004266


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


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 Ann Marie Rubin 2018-11-14 18:15:04 UTC

Per Tony Breeds: IPMI Driver errors out when talking to an OpenBMC BMC.

Comment 16 errata-xmlrpc 2019-01-11 11:54:45 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/RHEA-2019:0045