Red Hat Satellite engineering is moving the tracking of its product development work on Satellite 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 "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. 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 "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-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.

Description of problem:

RHEL is considering a change to cease publishing uncompressed comps.xml metadata in the future.  While this is unlikely to happen soon, we need to stop expecting  package groups metadata to be available in uncompressed form.  Likewise we should produce both types of metadata to maintain compatibility with all releases.

https://bugzilla.redhat.com/show_bug.cgi?id=2056318


Version-Release number of selected component (if applicable): any


How reproducible:100%


Steps to Reproduce:
1.  Produce a repository with package groups but without a raw comps.xml file.  This might require manual modification as I believe createrepo_c typically creates both.
2.  Sync it
3.  The package group metadata (comps.xml) isn't processed and isn't available after republishing


Expected results:

It should be available and contain equivalent metadata as when it was synced.  Depending on our implementation decisions we should possibly produce both compressed and uncompressed comps metadata (TBD)



Additional info:

Removing the RFE tag because it's not really an RFE per-se, and if RHEL goes through with the change it would be a serious gap (though they are not likely to make the change on a short timescale for this reason)

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 (Important: Satellite 6.13 Release), 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/RHSA-2023:2097