Actions
Bug #39249
openRecover from false registration failures caused by TCP reset at high concurrency
Status:
Ready For Testing
Priority:
Normal
Assignee:
-
Category:
-
Target version:
-
Description
At 320+ concurrent host registrations, the server sometimes creates the Candlepin consumer record successfully but the TCP connection is reset before the response reaches subscription-manager. This causes subscription-manager to report failure even though the registration succeeded server-side.
Adds a recovery check after subscription-manager register fails: runs subscription-manager identity to detect whether the host was actually registered, and if so treats the registration as successful rather than triggering a retry loop.
Updated by The Foreman Bot about 2 months ago
- Status changed from New to Ready For Testing
- Pull request https://github.com/theforeman/foreman/pull/10948 added
Updated by Pablo Méndez Hernández about 2 months ago
- Red Hat JIRA set to SAT-44625
Actions