Bug 2152709
Summary: | Concurrent registration of hosts behind a Capsule fail with error 502 | ||
---|---|---|---|
Product: | Red Hat Satellite | Reporter: | Pablo Mendez Hernandez <pmendezh> |
Component: | Installation | Assignee: | Ewoud Kohl van Wijngaarden <ekohlvan> |
Status: | CLOSED ERRATA | QA Contact: | Satellite QE Team <sat-qe-bz-list> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 6.13.0 | CC: | ahumbe, egolov, ehelms, ekohlvan, jhutar, rlavi |
Target Milestone: | 6.15.0 | Keywords: | Patch, Performance, Triaged |
Target Release: | Unused | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | foreman-installer-3.9.0-0 | Doc Type: | If docs needed, set a value |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2024-04-23 17:12:54 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
Pablo Mendez Hernandez
2022-12-12 18:54:55 UTC
We can set https://httpd.apache.org/docs/current/mod/mod_proxy.html#proxytimeout via the Hiera key apache::mod::proxy::proxy_timeout. Would this be sufficient for your needs and able to close out the bug? I'd (and a lot of customers I'd say) prefer to tackle every possible timeout individually instead of using such a big hammer, so I'd like to keep it open. Hi Pablo, Is this something that could be captured within the tuning guide for now? Thanks! Hi Brad, I'll make sure to create an issue to include the document in the KCS into the Tuning Guide. Some initial testing of https://github.com/theforeman/puppet-foreman_proxy_content/pull/442 shows that using HTTP/2 in the Capsule -> Satellite communication makes it much more reliable. Upstream bug assigned to ekohlvan Upstream bug assigned to ekohlvan Moving this bug to POST for triage into Satellite since the upstream issue https://projects.theforeman.org/issues/36854 has been resolved. Bulk setting Target Milestone = 6.15.0 where sat-6.15.0+ is set. Due to the registrations number improvements in our testing shown in https://github.com/theforeman/puppet-foreman_proxy_content/pull/442#issuecomment-1776993907, I'm setting VERIFIED on the patch. There have been multiple changes through our most recent releases targeted at helping to reduce the occurrence of this issue. The nature of this issue is that even at certain scales, or certain loads that it might be possible to trigger this particular error code. We have decided to close this as done in Satellite 6.15 given the, in part, the breadth of the attached issues. If you encounter this issue on a supported version of Satellite please open a new bug that is specific to your particular issue and that targets the workload you are performing when it occurs. Please include as much detail as possible about what you were trying to do, how many hosts or actions were involved, CPU count, memory, the version of Satellite and details that help to indicate how to reproduce it. This will help us to investigate the issue and not the symptom. 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.15.0 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-2024:2010 |