Bug 1808368

Summary:	Sync task should immediately fail - current behavior seems to be a timeout.
Product:	Red Hat Satellite	Reporter:	Ram Nainsingh Tiruwa <ramsingh>
Component:	Pulp	Assignee:	satellite6-bugs <satellite6-bugs>
Status:	CLOSED ERRATA	QA Contact:	Lai <ltran>
Severity:	low	Docs Contact:
Priority:	unspecified
Version:	6.6.0	CC:	ahumbe, aruzicka, bmbouter, dalley, dkliban, ggainey, ipanova, jsherril, ltran, rchan, ttereshc
Target Milestone:	6.10.0	Keywords:	Triaged
Target Release:	Unused
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2021-11-16 14:09:07 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 Ram 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

Comment 3 Justin Sherrill 2020-03-11 02:06:30 UTC

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?

Comment 5 Justin Sherrill 2020-03-24 15:22:14 UTC

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?

Comment 6 Brian Bouterse 2020-03-30 18:58:24 UTC

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 7 pulp-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 8 pulp-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 9 Tanya 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.

Comment 14 Lai 2021-08-23 17:34:35 UTC

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

Comment 17 errata-xmlrpc 2021-11-16 14:09:07 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 (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