Bug 2123593

Summary:	Satellite should be able to process (and publish) compressed comps.xml / groups metadata
Product:	Red Hat Satellite	Reporter:	Daniel Alley <dalley>
Component:	Pulp	Assignee:	satellite6-bugs <satellite6-bugs>
Status:	CLOSED ERRATA	QA Contact:	Vladimír Sedmík <vsedmik>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	6.11.0	CC:	ahumbe, dkliban, ggainey, msunil, pcreech, rchan, saydas, zhunting
Target Milestone:	6.13.0	Keywords:	Triaged
Target Release:	Unused
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	pulp_rpm-3.18.11, pulp_rpm-3.17.16	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2023-05-03 13:21:46 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:

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