Description of problem: Satellite UI shows 0 packages\errata\package_groups after a bad sync followed by a successful sync for the same repo Version-Release number of selected component (if applicable): Satellite 6.10 [ satellite-6.10.0-0.6.beta.el7sat.noarch ] How reproducible: Under specific circumstances Steps to Reproduce: 1. Build a satellite 6.10, import manifest and enable RHEL 7Server, RHEL EUS 7.7, RHEL 6 ELS, RHEL 7 Optional repos. 2. Sync them at once and let the sync get failed [ Could be because of https://bugzilla.redhat.com/show_bug.cgi?id=1993773 ] 3. Now sync them individually one by one, and ensure that sync gets completed for all of them. 4. Go to Content --> Products --> Click open the concerned product and see the counts 5. Republish Repository metadata for an affected repo 6. Repeate Step 4 for one of the affected repo 7. Register a system with satellite, enable the affected repo on it and check "yum repolist" Actual results: At Step 4 and 6, we will be able to see 0 packages reflected in UI for those repos. At Step 7, yum will be able to show proper count of the packages from the same broken repo as well as will be able to download content from there. Expected results: With second successful sync, pulp3 + katello should be able to update the count of package\errata\package_groups in UI properly Additional info: * I noticed this happening for big yum repos mostly i.e. > 25 GB repos * Task export , syslog , production.log and screenshots will be attached next
So as mentioned above, Normal sync will not fix anything. I could only fix it by doing "Advanced Sync --> Complete Sync" .. And Hopefully, if I would have done "Validate Content Sync" that would have fixed the issue as well but obviously it would have downloaded all rpms as well . So normal Sync itself should be able to fix this issue.
Closing this as the cloned issue was addressed in 6.8.
Sorry closed the wrong issue.
Created redmine issue https://projects.theforeman.org/issues/33443 from this bug
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 (Moderate: Satellite 6.10 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-2021:4702