Project

General

Profile

Actions

Bug #39229

open

Net::HTTP read_timeout not applied from foreman_request_timeout setting

Added by Pablo Méndez Hernández 4 months ago. Updated 3 months ago.

Status:
Ready For Testing
Priority:
Normal
Assignee:
-
Category:
-
Target version:
-
Difficulty:
Triaged:
No
Fixed in Releases:
Found in Releases:

Description

ForemanRequest uses a bare Net::HTTP instance whose read_timeout defaults to Ruby's hardcoded 60s. Under high-concurrency registration load this causes 500 errors when Foreman takes longer than 60s to process POST /register.

Fix

Introduces :foreman_request_timeout and documents it in settings.yml.example, then applies it to http.read_timeout in ForemanRequest#http_init when configured and greater than zero. The respond_to? guard preserves backward compatibility when the setting is absent.

subscription-manager's default server_timeout is 180s, so values above that are recommended to avoid cutting connections the client is still waiting on.

Actions #1

Updated by Pablo Méndez Hernández 4 months ago

  • Description updated (diff)
Actions #2

Updated by Pablo Méndez Hernández 4 months ago

  • Description updated (diff)
Actions #3

Updated by The Foreman Bot 4 months ago

  • Status changed from New to Ready For Testing
  • Pull request https://github.com/theforeman/smart-proxy/pull/936 added
Actions #4

Updated by Pablo Méndez Hernández 3 months ago

  • Red Hat JIRA set to SAT-44912
Actions

Also available in: Atom PDF