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.
Bug 2123593 - Satellite should be able to process (and publish) compressed comps.xml / groups metadata
Summary: Satellite should be able to process (and publish) compressed comps.xml / grou...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Pulp
Version: 6.11.0
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: 6.13.0
Assignee: satellite6-bugs
QA Contact: Vladimír Sedmík
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-09-02 04:05 UTC by Daniel Alley
Modified: 2024-10-08 09:28 UTC (History)
9 users (show)

Fixed In Version: pulp_rpm-3.18.11, pulp_rpm-3.17.16
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-05-03 13:21:46 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
Hotfix RPM for Satellite 6.11.5 on RHEL 8 (382.64 KB, application/x-rpm)
2024-05-22 21:26 UTC, wclark
no flags Details
Hotfix RPM for Satellite 6.11.5 on RHEL 7 (398.12 KB, application/x-rpm)
2024-05-22 21:28 UTC, wclark
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Github pulp pulp_rpm issues 2753 0 None closed Be able to process (and publish) compressed comps.xml / groups metadata 2023-02-16 20:30:42 UTC
Red Hat Bugzilla 2056318 0 unspecified CLOSED createrepo_c creates two group definition compressed comps.xml.gz and uncompressed comps.xml in repodata 2023-09-27 16:45:42 UTC
Red Hat Issue Tracker SAT-14797 0 None None None 2023-01-06 20:55:24 UTC
Red Hat Knowledge Base (Solution) 7070877 0 None None None 2024-05-20 10:00:29 UTC
Red Hat Product Errata RHSA-2023:2097 0 None None None 2023-05-03 13:21:59 UTC

Description Daniel Alley 2022-09-02 04:05:31 UTC
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:

Comment 1 Daniel Alley 2022-09-02 13:53:36 UTC
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)

Comment 12 errata-xmlrpc 2023-05-03 13:21:46 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 (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

Comment 13 wclark 2024-05-22 21:26:07 UTC
Created attachment 2034695 [details]
Hotfix RPM for Satellite 6.11.5 on RHEL 8

A hotfix RPM is now available for Satellite 6.11.5 on RHEL 8.

Installation instructions:

1. Create a backup or snapshot of the Satellite server.

2. Download the hotfix RPM python38-pulp-rpm-3.17.10-3.HOTFIXRHBZ2123593.el8pc.noarch.rpm from this attachment and copy it to Satellite server

3. # dnf install ./python38-pulp-rpm-3.17.10-3.HOTFIXRHBZ2123593.el8pc.noarch.rpm --disableplugin=foreman-protector

4. # satellite-maintain service restart

Comment 14 wclark 2024-05-22 21:28:02 UTC
Created attachment 2034696 [details]
Hotfix RPM for Satellite 6.11.5 on RHEL 7

A hotfix RPM is now available for Satellite 6.11.5 on RHEL 7.

Installation instructions:

1. Create a backup or snapshot of the Satellite server.

2. Download the hotfix RPM tfm-pulpcore-python3-pulp-rpm-3.17.10-3.HOTFIXRHBZ2123593.el7pc.noarch.rpm from this attachment and copy it to Satellite server

3. # yum install ./tfm-pulpcore-python3-pulp-rpm-3.17.10-3.HOTFIXRHBZ2123593.el7pc.noarch.rpm --disableplugin=foreman-protector

4. # satellite-maintain service restart

Comment 15 Sayan Das 2024-05-23 07:45:28 UTC
Tested the hotfixes and updated the solution article with relevant information

Katello::Errors::Pulp3Error: Fatal parser error while syncing EPEL repository in Red Hat Satellite 6.11 - Red Hat Customer Portal
https://access.redhat.com/solutions/7070877


Note You need to log in before you can comment on or make changes to this bug.