Bug 2227897

Summary:	Importing incremental content not recreating metadata properly
Product:	Red Hat Satellite	Reporter:	Odilon Sousa <osousa>
Component:	Inter Satellite Sync	Assignee:	Partha Aji <paji>
Status:	VERIFIED ---	QA Contact:	Cole Higgins <chiggins>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	6.12.1	CC:	juwatts, rlavi
Target Milestone:	6.12.5	Keywords:	Triaged
Target Release:	Unused
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	tfm-rubygem-katello-4.5.0.35-1	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:		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 Odilon Sousa 2023-07-31 19:20:29 UTC

Description of problem:

On Satellite 6.12, importing an incremental export does not update the metadata properly on pulp.

User can see the updated number of packages on the webUI, but clients consuming the repository still see the old count (from before importing the incremental).

Forcing pulp to regenerate the metadata does create it properly and clients can then see the added packages.

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

6.12.2

How reproducible:
I managed to reproduce it using RHEL 8 AppStream repository. Exporting a custom repository worked fine. I'm working to get a complete + incremental of a smaller Red Hat repository, so we can run tests faster.

Steps to Reproduce:
1. Do complete export of a Red hat repository
2. Import complete on disconnected Satellite
3. Run "dnf repolist -v" on a client that consumes the repository
4. Export incremental of the same repository
5. Import incremental
6. On the client "dnf clean all && dnf repolist -v". Same number of packages as on step 3 are seen.


Actual results:
After incremental import, packages are not available for clients.

Expected results:
Added packages should be available for clients.


Additional info:

Comment 1 Bryan Kearney 2023-07-31 20:03:41 UTC

Upstream bug assigned to paji

Comment 2 Bryan Kearney 2023-07-31 20:03:43 UTC

Moving this bug to POST for triage into Satellite since the upstream issue https://projects.theforeman.org/issues/36164 has been resolved.