RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

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 ...

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

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

S

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.

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.

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