Bug 1948930

Summary: Discrepancy in the packages count in a repository on the client and Satellite
Product: Red Hat Satellite Reporter: rakesh kumar <rakumar>
Component: PulpAssignee: satellite6-bugs <satellite6-bugs>
Status: CLOSED CURRENTRELEASE QA Contact: Vladimír Sedmík <vsedmik>
Severity: high Docs Contact:
Priority: high    
Version: 6.8.0CC: aganbat, ahumbe, asalvati, dalley, dhjoshi, ggainey, gpadholi, ipanova, jsherril, msunil, pdwyer, sadas, saydas, ttereshc, vcojot
Target Milestone: UnspecifiedKeywords: PrioBumpGSS
Target Release: Unused   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2023-01-23 14:58:59 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 rakesh kumar 2021-04-13 05:34:58 UTC 
Description of problem:

Sometimes the number of packages on the client in a repository(could be any repo like RHEL7 base) are less(at times it's only 100-200 only), there are no filters in the content view, content view publishes task completely without any issue and last repo sync was also successful.


Validate sync of the repository and publishing the content view again helps to resolve such issues but what is the cause of such issue, we should prevent such issues(metadata corruption) from happening in the product itself.


Version-Release number of selected component (if applicable):
All active versions.

How reproducible:
Sometimes
Comment 22 Justin Sherrill 2021-05-10 17:56:33 UTC 
Also, how much memory do th
Comment 55 Daniel Alley 2022-10-19 18:56:17 UTC 
We haven't seen this since Satellite 6.10, it seems to be fixed by Pulp 3.  Requesting verification before setting to CLOSED-CURRENTRELEASE.

For Satellite 6.8 and 6.9 the workaround seems to be "Republish Repository Metadata" or "Validate Content Sync" - this seems to work pretty reliably.
Comment 56 Daniel Alley 2022-10-19 18:57:53 UTC 
I strongly encourage an upgrade to 6.11 or (soon) 6.12 for any customers still encountering this.
Comment 57 Vladimír Sedmík 2022-11-30 13:33:55 UTC 
I haven't been able to reproduce the issue with the 6.12 Satellite.
Marking as Verified and proposing to CLOSED-CURRENTRELEASE.
Comment 59 Brad Buckingham 2023-01-23 14:58:59 UTC 
This bugzilla was remaining open only to track the issue for 6.9.z, in case a fix was needed there.  At this time 6.9 is EOL; therefore, moving to CLOSED:CURRENTRELEASE.