Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

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.

Bug 1837369

Summary:	dnf does not consider newer module versions when a new context is added - perl:5.24 EOL
Product:	Red Hat Enterprise Linux 8	Reporter:	Jaroslav Mracek <jmracek>
Component:	dnf	Assignee:	Packaging Maintenance Team <packaging-team-maint>
Status:	CLOSED CURRENTRELEASE	QA Contact:	swm-qe
Severity:	unspecified	Docs Contact:
Priority:	high
Version:	8.4	CC:	astepano, emrakova, james.antill, jblazek, jorton, jplesnik, lberton, mdomonko, ppisar, sct
Target Milestone:	rc	Keywords:	Triaged
Target Release:	8.2	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:	1757460	Environment:
Last Closed:	2021-09-06 10:15:46 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:
Bug Depends On:	1757460, 1763593
Bug Blocks:	1666770, 1713592, 1825061

Comment 4 Jaroslav Mracek 2021-09-06 10:15:46 UTC

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.

Comment 5 Petr Pisar 2021-09-06 11:48:44 UTC

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.

Comment 6 Petr Pisar 2021-09-08 11:14:24 UTC

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.