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 1666871

Summary:	libmodulemd should ignore defaults for modules with defaults conflicts
Product:	Red Hat Enterprise Linux 8	Reporter:	Petr Šabata <psabata>
Component:	libmodulemd	Assignee:	Stephen Gallagher <sgallagh>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Karel Srot <ksrot>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	8.0	CC:	jblazek, sgallagh, wchadwic
Target Milestone:	rc	Flags:	rule-engine: mirror+
Target Release:	8.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	libmodulemd-2.0.0-5.el8	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-06-14 00:47:13 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:
Bug Blocks:	1656019

Description Petr Šabata 2019-01-16 19:59:52 UTC

Today libmodulemd throws an error when it encounters a module defaults conflict it cannot resolve, for instance if two repositories with the same priority contain modulemd-defaults with identical version yet different content.

This results in a DNF error the user cannot effectively do anything about besides disabling one of the repositories.  We decided to change the behavior to ignore the conflict instead, and report a warning.

This affects the available package set but has no impact on users already consuming the content and having a stream enabled.  Users can also still pick a stream manually.

Extra notes:

* QE tests might need to be updated.

* Since this changes the available package set, ursine packages that depend on packages provided by the affected module will not be installable until the situation is resolved.