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.
DescriptionRam Nainsingh Tiruwa
2020-02-28 10:57:28 UTC
Task status for repository sync is showing warning instead of Error
Satellite 6.6
syncing repository with proxy in the Environment having a connection issue for the upstream URL.
Actual results:
Sync task is getting timeout
Expected results:
Sync task should immediately fail
Ram
Can you provide some reproducer steps or anything that could help us with this?
What http code was the upstream proxy throwing? How long did it take to fail (as you mentioned it wasn't immediate)?
Do you have a task export showing the particular task?
Pulp team, it looks like pulp is retrying after getting a 407. That seems safe to completely cancel the sync, which i think we do for other http codes. Any thoughts?
I believe cancelling on a 407 response is the right thing to do because no amount of retrying will present credentials to the proxy that weren't there to start with.
Comment 7pulp-infra@redhat.com
2020-03-31 17:48:00 UTC
The Pulp upstream bug status is at NEW. Updating the external tracker on this bug.
Comment 8pulp-infra@redhat.com
2020-03-31 17:48:01 UTC
The Pulp upstream bug priority is at Normal. Updating the external tracker on this bug.
Comment 9Tanya Tereshchenko
2021-04-19 17:16:58 UTC
Pulp 2 is in maintenance mode, I'm repurposing this BZ to check that HTTP 407 is handled correctly in Pulp 3.
Steps to verify
1. Set up a proxy and ensure that it can get regular http request without issues
2. On the satellite, setup the proxy: Infrastructure -> HTTP Proxies -> New HTTP Proxy and create the proxy on the UI
3. save the proxy
4. Create custom repo and change the "HTTP proxy field" to use the proxy created in step 1
5. Sync repo
Expected:
Syncing should failed immediately
Actual:
Syncing failed immediately with error message "Cannot connect to host"
Marking verified on 6.10 snap 14
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