Actions
Bug #22540
closed
Connection timeout to server are too long
Pull Request:
Severity:
Major - prevents use of part of Rudder | no simple workaround
UX impact:
It bothers me each time
User visibility:
Operational - other Techniques | Rudder settings | Plugins
Effort required:
Priority:
63
Name check:
To do
Fix check:
Checked
Regression:
No
Description
When an agent tries to connect to the server, there is a long timeout.
When it runs it policies or when it updates, there is a timeout, all those timeouts add up.
If the sum of timeout is more than 5mn, then when the server is unreachable, agents pile up on the node.
Updated by Benoît PECCATTE about 1 year ago
- Subject changed from Connection timeout to server ar too long to Connection timeout to server are too long
Updated by Benoît PECCATTE about 1 year ago
- Severity set to Major - prevents use of part of Rudder | no simple workaround
- UX impact set to It bothers me each time
- User visibility set to Operational - other Techniques | Rudder settings | Plugins
- Priority changed from 0 to 64
Updated by Benoît PECCATTE about 1 year ago
- Status changed from New to In progress
- Assignee set to Benoît PECCATTE
Updated by Benoît PECCATTE about 1 year ago
- Status changed from In progress to Pending technical review
- Assignee changed from Benoît PECCATTE to Alexis Mousset
- Pull Request set to https://github.com/Normation/rudder-techniques/pull/1809
Updated by Benoît PECCATTE about 1 year ago
- Status changed from Pending technical review to Pending release
Applied in changeset rudder-techniques|d9aeea4dad7c11d3f9ee716db8d9f02d15251695.
Updated by 
Updated by
Updated by Vincent MEMBRÉ 12 months ago
- Status changed from Pending release to Released
- Priority changed from 64 to 63
This bug has been fixed in Rudder 7.2.6 and 7.3.1 which were released today.
Actions