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.

The bug was created as remainder of the future issue with EOL. The issue is related to multi context streams (e.g. perl-DBI). The issue will be handled by additional data in future releases => copy of modules with the only changed version. It means outside of DNF and the solution will be not verified by our QE. The workflow with artificial module is already used (new contexts requiring perl-5.30), therefore closing it.

The workflow with artificial module was a hack nobody wants to repeat. I hoped this issue could be resolved in the means of static-context builds.

I was told by Jaroslav Mracek that static context is not supported in RHEL 8 (bug #1708589 comment#25) because:

It is an untested change.

Delivering a sparse matrix of static contexts of the affected modules would not retroactively fixed historical DNF we released in RHEL 8 GA. GA DNF is required to handle any future repository content. Therefore the artificial module builds would have to be injected to the repository and installation DVD unles the the GA DNF requirement is ceased.