Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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:
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
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.
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.