Bug 1976395

Summary:	lshw output may not be processed properly resulting in introspection memory being misreported
Product:	Red Hat OpenStack	Reporter:	Julia Kreger <jkreger>
Component:	openstack-ironic-python-agent	Assignee:	Julia Kreger <jkreger>
Status:	CLOSED ERRATA	QA Contact:	Paras Babbar <pbabbar>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	16.2 (Train)	CC:	aija.jaunteva, gael_rehault, kurt_hey, msecaur, richard.pioso, rlondhe, sbaker
Target Milestone:	z2	Keywords:	Triaged
Target Release:	16.2 (Train on RHEL 8.4)
Hardware:	Unspecified
OS:	All
Whiteboard:
Fixed In Version:	openstack-ironic-python-agent-5.0.5-2.20220106024842.df187ae.el8ost	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2022-03-23 22:10:48 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 Julia Kreger 2021-06-25 22:53:51 UTC

Description of problem:

An issue in the lshw package can cause memory reporting from inspection to fail.
A full description is available in the original fix to work around this issue, located at https://review.opendev.org/c/openstack/ironic-python-agent/+/788588.

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


The issue in lshw is present in lshw = B.02.19.2-5.el8 and ultimately code to handle this issue in ironic-python-agent needs to be backported to a Train based release to handle the lshw package issue.


How reproducible:

Unknown. This was apparently found upstream by the OpenShift IPI Metal team, the fix was just not backported to the stable/train branch. Running a stable/train branch version on RHEL 8.4 exposes OSP to this potential failure case, and the most appropriate action is to backport the upstream fix into our builds.

Comment 7 Matthew Secaur 2021-12-10 15:52:00 UTC

I actually have this issue 100% of the time in my lab when building OSP16.2 (including 16.2.1 that was released late yesterday). Although we have a workaround [1], I would like to request that this fix be backported to OSP16.2.1.

[1] https://access.redhat.com/solutions/6568411

Comment 8 Steve Baker 2021-12-14 21:18:20 UTC

The fix is on track for being released in 16.2.2.

Comment 9 Matthew Secaur 2021-12-15 17:57:25 UTC

@sbaker 

Thanks. I am aware of that. I am asking that it be backported to OSP16.2.1.

Comment 18 errata-xmlrpc 2022-03-23 22:10:48 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 (Release of components for Red Hat OpenStack Platform 16.2.2), 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-2022:1001