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.

Hi John,
This is a clone of Bug #1404137, for 7.3.z.
But the flag is rhel7.4, and i can not change it.
Do you have permission to change it ?  or other people can do it ?
Thanks a lot !


Best Wishes
Yanan Fu

Hi Yanan Fu;

This is indeed a bug and could be fixed in 7.3.z, however the required work to fix it in our downstream 2.6.0-based version would be too great and a new solution would essentially have to be re-architected.

I attempted a backport of the necessary fix but it's too much code to backport to a stable release. I humbly recommend that anyone who encounters this issue upgrade to the 7.4 release instead if possible.

That said, if a customer does run into this issue, please re-open this BZ and I will put in the necessary work to reimplement a solution.

Thank you,
--John Snow