Description of problem: Satellite syncs receive pulp RPM1004 error and http 403 Forbidden errors at unpredictable times when syncing from the CDN. How reproducible: Not yet reproducible in any reliable way (short of purposefully breaking certificates). Actual results: Syncs receive RPM1004 errors from pulp (http 403 errors) when retrieving Red Hat content from the CDN. Expected results: RPM1004 errors when syncing should be either eliminated or reliably able to be predicted.
The problem of receiving 403s when syncing Red Hat content is most commonly resolved by either: 1) refreshing the Satellite manifest in Content > Red Hat Subscriptions > Manage Manifest > Refresh Manifest or 2) foreman-rake katello:refresh_pulp_repo_details More troubleshooting information found in this kcs: https://access.redhat.com/solutions/3047741
Connecting redmine issue https://projects.theforeman.org/issues/29367 from this bug
As part of this bug we are working to proactively notify users (via the notification drawer system) when we've detected that a manifest is no longer valid as well as providing instructions for how to resolve the situation (refresh the manifest). We still have not been able to reproduce the issue where by certs are not updated in pulp. I have opened a 2nd bugzilla here: https://bugzilla.redhat.com/show_bug.cgi?id=1814330 to track this issue.
Moving this bug to POST for triage into Satellite 6 since the upstream issue https://projects.theforeman.org/issues/29367 has been resolved.
Verified in satellite-6.8.0-0.7.beta.el7sat.noarch pulp-server-2.21.2-1.el7sat.noarch
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.8 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-2020:4366