Actions
Bug #22339
closed
Hook timeout may not have the good value
Status:
Released
Priority:
N/A
Assignee:
Category:
Web - Config management
Target version:
Pull Request:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
0
Name check:
To do
Fix check:
Checked
Regression:
No
Description
We have inverted a value for sync run of hooks between warn and kill timeout.
This mostly affects tests, but also node acceptance hooks.
We also have too much errors on our ci about timeout so let's augment them to 5 seconds
Updated by Vincent MEMBRÉ about 1 year ago
- Related to Bug #18915: We don't know when generation hooks takes more time than expected, massively impacting generation time added
Updated by Vincent MEMBRÉ about 1 year ago
- Status changed from New to In progress
- Assignee set to Vincent MEMBRÉ
Updated by Vincent MEMBRÉ about 1 year ago
- Status changed from In progress to Pending technical review
- Assignee changed from Vincent MEMBRÉ to François ARMAND
- Pull Request set to https://github.com/Normation/rudder/pull/4653
Updated by Vincent MEMBRÉ about 1 year ago
- Status changed from Pending technical review to Pending release
Applied in changeset rudder|b678a4af3828decb9bcae4c2d65e9bd4c74bd0ae.
Updated by François ARMAND about 1 year ago
- Fix check changed from To do to Checked
Check that it works as expected in policy generation hooks with defining :
HOOK_WARN_TIMEOUT = 1s HOOK_KILL_TIMEOUT = 5s
Updated by Alexis Mousset 9 months ago
- Status changed from Pending release to Released
Actions