Actions
Bug #39229
openNet::HTTP read_timeout not applied from foreman_request_timeout setting
Status:
Ready For Testing
Priority:
Normal
Assignee:
-
Category:
-
Target version:
-
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.
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