Bug 1991051

Summary:	Add gating tests for fio
Product:	Red Hat Enterprise Linux 9	Reporter:	Eric Sandeen <esandeen>
Component:	fio	Assignee:	Eric Sandeen <esandeen>
Status:	CLOSED ERRATA	QA Contact:	Samuel Petrovic <spetrovi>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	CentOS Stream	CC:	jhladky, spetrovi, xzhou
Target Milestone:	beta	Keywords:	Triaged
Target Release:	9.0	Flags:	pm-rhel: mirror+
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2022-05-17 14:09:51 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 Eric Sandeen 2021-08-06 21:38:03 UTC

I can't do any further fio updates until gating is added (gating was inexplicably dropped from rhel8->rhel9) so, filing the requisite bug so I can copy over the tests from rhel8 ...

Comment 1 Eric Sandeen 2021-08-06 21:40:19 UTC

Hi Samuel, I need your qe_ack permission here as well.

Comment 3 Samuel Petrovic 2021-08-09 09:56:35 UTC

Got it. Please feel free to set ITM as well.

S

Comment 6 Eric Sandeen 2021-08-18 14:49:46 UTC

Sigh. I had not put this into modified, because I was waiting a few days (!) for the built gto complete, due to our increasingly fragile infrastructure.

The aarch64 build was ultimately canceled, but the gating is checked in now. Gating also does not impact package functionality in any way, this is just a check-box item for process.

So I'm not sure there's anything else that actually needs to be done to resolve this bug, despite the infrastructure failure.

Comment 10 Eric Sandeen 2021-08-26 14:22:46 UTC

Yes. This has no bearing whatsoever on beta. I had to add tests before I could fix the FTBFS.  They could both be pushed out.

Comment 16 errata-xmlrpc 2022-05-17 14:09:51 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 (new packages: fio), 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:2659