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.

rhel-8.6.0 machine types need to be added for all supported architectures.

Connie - since you added w/ ITR and seem to be tracking, I added you as owner and used the Tracking keyword - we probably could have just created an epic. I think you'll also note that this bug doesn't fall under stale bug autoclosure now, so once all the bugs are in verified you will need to close this yourself...

*** Bug 1998945 has been marked as a duplicate of this bug. ***

(In reply to John Ferlan from comment #1)
> Connie - since you added w/ ITR and seem to be tracking, I added you as
> owner and used the Tracking keyword - we probably could have just created an
> epic. I think you'll also note that this bug doesn't fall under stale bug
> autoclosure now, so once all the bugs are in verified you will need to close
> this yourself...

Yes, it's fine to have this assigned to me.

Also note that I actually created this as an 'epic' type -- not sure if that has any useful consequences.

Moved to closed since all tracked bz's are in verified now on the release.