Bug 1664120

Summary:	capsule will pause for 60 seconds if connection to sat is servered, causing 502s
Product:	Red Hat Satellite	Reporter:	Chris Duryee <cduryee>
Component:	Installation	Assignee:	Eric Helms <ehelms>
Status:	CLOSED ERRATA	QA Contact:	Devendra Singh <desingh>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	6.4	CC:	aruzicka, ehelms, inecas, kabbott, zhunting
Target Milestone:	6.10.0	Keywords:	Triaged
Target Release:	Unused
Hardware:	Unspecified
OS:	Unspecified
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:08:28 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 Chris Duryee 2019-01-07 18:58:05 UTC

Description of problem:

The capsule does a ProxyPass up to the Satellite to pass through API calls. By default, the ProxyPass will hold a connection open and re-use it instead of making a new connection each time.

However, by default, if the connection is interrupted, ProxyPass will wait 60 seconds before trying a server again since it assumes there are multiple workers in a pool and not just one Satellite. During this time, clients will get a "502 proxy error" from the capsule.

The ProxyPass up to the Satellite should likely have the options "retry=0 disablereuse=On". This will make a new connection each time.


Version-Release number of selected component (if applicable): 6.4


How reproducible: extremely difficult to repro

Comment 6 Lukas Zapletal 2019-01-09 09:38:20 UTC

Thanks for the extensive analysis, looks sane to add this. However I think this is more Installer component than Capsule which is meant to be for Smart-Proxy (Ruby) codebase rather than configuration things. Switching.

Comment 9 Mike McCune 2021-03-11 18:51:17 UTC

Upon review of our valid but aging backlog the Satellite Team has concluded that this Bugzilla does not meet the criteria for a resolution in the near term, and are planning to close in one month's time. If you have any concerns about this, please contact your Red Hat Account team.  Thank you.

Comment 10 Eric Helms 2021-03-22 16:59:23 UTC

Created redmine issue https://projects.theforeman.org/issues/32161 from this bug

Comment 11 Bryan Kearney 2021-03-23 12:06:30 UTC

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

Comment 17 Devendra Singh 2021-07-19 17:51:53 UTC

Verified on 6.10 Snap9

Verification points

1- Installed satellite and capsule with 6.10 Snap9
2- Prepared one RHEL7.9 client.
3- Paused the httpd client on the sat (using "systemctl stop httpd")
4- Registered the capsule with the client and it gets failed without any wait time with an "internal server error".

[root@xyz ~]# date;curl -sS --insecure 'https://xyz:9090/register?activation_keys=ak_7&lifecycle_environment_id=2&location_id=2&operatingsystem_id=1&organization_id=1' -H 'Authorization: Bearer eyJhbGciOiJIUzI1NiJ9.eyJ1c2VyX2lkIjo0LCJpYXQiOjE2MjY2Nzk3NjgsImp0aSI6Ijk2ZDY2OTNmNWU0N2JjZTY1ZGVmZWI1NzJjYzk1NDAxZDlkNTBjZTc4MWQwNzA1MjhlYzA5NzI2NDMxYzk1YjIiLCJleHAiOjE2MjY2OTQxNjgsInNjb3BlIjoicmVnaXN0cmF0aW9uI2dsb2JhbCByZWdpc3RyYXRpb24jaG9zdCJ9.HEYGK5R6hkBZ-HvW5Fre7m3mEcW6ui5YgvJt9fEOBCE' | bash;date
Mon Jul 19 03:29:50 EDT 2021
Internal Server Error
Mon Jul 19 03:29:50 EDT 2021

Comment 20 errata-xmlrpc 2021-11-16 14:08:28 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