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.
The Pulp upstream bug status is at NEW. Updating the external tracker on this bug.
The Pulp upstream bug priority is at Normal. Updating the external tracker on this bug.
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