Bug 1733650

Summary:	Satellite receives RPM1004 pulp error and 403 Forbidden http error retrieving packages from CDN
Product:	Red Hat Satellite	Reporter:	Paul Dudley <pdudley>
Component:	Repositories	Assignee:	Justin Sherrill <jsherril>
Status:	CLOSED ERRATA	QA Contact:	Bruno Rocha <rochacbruno>
Severity:	urgent	Docs Contact:
Priority:	high
Version:	6.5.0	CC:	ahumbe, cdonnell, cmarinea, dsynk, egolov, gscarbor, jbhatia, jsenkyri, jsherril, jturel, ktordeur, kupadhya, pdwyer, rcavalca, sadas, saydas, smajumda, swadeley, vhernand, vmeghana, wclark
Target Milestone:	6.8.0	Keywords:	PrioBumpGSS, PrioBumpQA, Triaged
Target Release:	Unused
Hardware:	x86_64
OS:	All
Whiteboard:
Fixed In Version:	tfm-rubygem-katello-3.16.0-0	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2020-10-27 12:58:49 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 Paul Dudley 2019-07-26 22:34:07 UTC

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.

Comment 4 Paul Dudley 2019-07-26 22:39:15 UTC

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

Comment 7 Justin Sherrill 2020-03-17 16:26:00 UTC

Connecting redmine issue https://projects.theforeman.org/issues/29367 from this bug

Comment 8 Justin Sherrill 2020-03-17 16:48:38 UTC

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.

Comment 9 Bryan Kearney 2020-03-20 20:06:18 UTC

Moving this bug to POST for triage into Satellite 6 since the upstream issue https://projects.theforeman.org/issues/29367 has been resolved.

Comment 10 Bruno Rocha 2020-08-05 20:38:41 UTC

Verified in satellite-6.8.0-0.7.beta.el7sat.noarch
pulp-server-2.21.2-1.el7sat.noarch

Comment 13 errata-xmlrpc 2020-10-27 12:58:49 UTC

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