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:
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
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.
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