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.
DescriptionStephen Gallagher
2019-09-24 21:16:48 UTC
Description of problem:
A third-party repository such as EPEL that wants to add a supplementary module stream to a module that is shipped by RHEL and enable a default profile for that stream will cause the defaults shipped by RHEL to be discarded.
Version-Release number of selected component (if applicable):
libmodulemd-2.5.0-2.el8
How reproducible:
Every time
Steps to Reproduce:
1. Pick a module shipped in RHEL 8 AppStream (e.g. "nodejs").
2. Create and build a new stream for that module (e.g "13").
3. Create a repository for the newly-built module with createrepo_c.
4. Produce a defaults document and append it to the repodata produced by the module build:
```
document: modulemd-defaults
data:
module: nodejs
modified: 201909240000
profiles:
11: [ "default" ]
```
(Make sure "modified" is a higher value than the one currently shipping in the RHEL AppStream repository.)
Actual results:
When the repository metadata from AppStream is merged with the additional repository, the defaults data from AppStream is lost, replaced by the one from the additional repository (or the reverse, if AppStream has a newer 'modified' value than the repo).
Expected results:
Non-conflicting profile defaults should be merged together. Conflicting profile defaults and default streams will be taken from the defaults document with the higher 'modified' value.
Additional info:
This bug exists in both the 1.x and 2.x APIs of libmodulemd.
Comment 1Stephen Gallagher
2019-11-05 20:57:51 UTC
*** This bug has been marked as a duplicate of bug 1761805 ***
Description of problem: A third-party repository such as EPEL that wants to add a supplementary module stream to a module that is shipped by RHEL and enable a default profile for that stream will cause the defaults shipped by RHEL to be discarded. Version-Release number of selected component (if applicable): libmodulemd-2.5.0-2.el8 How reproducible: Every time Steps to Reproduce: 1. Pick a module shipped in RHEL 8 AppStream (e.g. "nodejs"). 2. Create and build a new stream for that module (e.g "13"). 3. Create a repository for the newly-built module with createrepo_c. 4. Produce a defaults document and append it to the repodata produced by the module build: ``` document: modulemd-defaults data: module: nodejs modified: 201909240000 profiles: 11: [ "default" ] ``` (Make sure "modified" is a higher value than the one currently shipping in the RHEL AppStream repository.) Actual results: When the repository metadata from AppStream is merged with the additional repository, the defaults data from AppStream is lost, replaced by the one from the additional repository (or the reverse, if AppStream has a newer 'modified' value than the repo). Expected results: Non-conflicting profile defaults should be merged together. Conflicting profile defaults and default streams will be taken from the defaults document with the higher 'modified' value. Additional info: This bug exists in both the 1.x and 2.x APIs of libmodulemd.