Bug 1761805

Summary:	Merging modulemd-defaults from various repository
Product:	Red Hat Enterprise Linux 8	Reporter:	Remi Collet <fedora>
Component:	libmodulemd	Assignee:	Stephen Gallagher <sgallagh>
Status:	CLOSED ERRATA	QA Contact:	Jan Blazek <jblazek>
Severity:	high	Docs Contact:
Priority:	high
Version:	8.0	CC:	jwboyer, sgallagh, toneata, wchadwic
Target Milestone:	rc	Keywords:	AutoVerified, ZStream
Target Release:	8.0	Flags:	pm-rhel: mirror+
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	libmodulemd-2.5.0-4.el8	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:
Clones:	1763779 (view as bug list)		Environment:
Last Closed:	2020-04-28 16:44:34 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:	1763779

Description Remi Collet 2019-10-15 12:30:20 UTC

When multiple repositories provide different version of the same stream, default stream is lost, 

"dnf module list foo" don't have any default stream (with [d])

Use case

* AppStream providing php 7.2 (default stream = 7.2)
* CentOS Stream providing php 7.3
  (no default stream, as 7.2 from AppStream expected)

Other use case

* AppStream providing php 7.2 and 7.3
* remi-modular providing remi-7.2, remi-7.3, remi-7.4


Fixed uppstream, see 
See https://github.com/fedora-modularity/libmodulemd/issues/381
https://github.com/fedora-modularity/libmodulemd/pull/379

Comment 1 Stephen Gallagher 2019-10-15 12:42:05 UTC

As Remi notes, this is fixed upstream. This will be a serious issue for anyone managing a third-party repository providing modules (such as Remi's Repo and EPEL), so I'd call this a very high priority to fix in RHEL.

Comment 7 Stephen Gallagher 2019-11-05 20:57:51 UTC

*** Bug 1755148 has been marked as a duplicate of this bug. ***

Comment 12 errata-xmlrpc 2020-04-28 16:44:34 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHEA-2020:1790