Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.

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
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.