Actions
Bug #18530
closed
We don't know which hook timeout when it happens
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:
Description
So, we know that a hook timed out:
[2020-11-09 10:55:16+0100] ERROR policy.generation.manager - Error when updating policy, reason was: Error when executing hooks in directory '/opt/rudder/etc/hooks.d/policy-generation-finished'. <- Inconsistency: Hook ''/opt/rudder/etc/hooks.d/policy-generation-finished' with environment parameters: [[RUDDER_NODE_IDS:] [RUDDER_GENERATION_DATETIME:2020-11-09T09:55:09.633+01:00] [RUDDER_END_GENERATION_DATETIME:2020-11-09T09:55:16.078+01:00] [RUDDER_NODE_IDS_PATH:/var/rudder/policy-generation-info/last-updated-nodeids] [RUDDER_NUMBER_NODES_UPDATED:0] [RUDDER_ROOT_POLICY_SERVER_UPDATED:1]]' timed out after PT1H
We even have details about parameters leading to the timeout. But not WHICH hook timed out. So this is not actionnable and dumb.
Files
Updated by François ARMAND over 3 years ago
- Status changed from New to In progress
Updated by François ARMAND over 3 years ago
- Status changed from In progress to Pending technical review
- Assignee changed from François ARMAND to Nicolas CHARLES
- Pull Request set to https://github.com/Normation/rudder/pull/3348
Updated by François ARMAND over 3 years ago
- Status changed from Pending technical review to Pending release
Applied in changeset rudder|20f6d5925ea3af4579d1b7dff89eac749f69ee93.
Updated by François ARMAND over 3 years ago
- Fix check changed from To do to Error - Blocking
It seems that timeout doesn't work anymore
Updated by François ARMAND over 3 years ago
- File clipboard-202012021829-umzwf.png clipboard-202012021829-umzwf.png added
- Fix check changed from Error - Blocking to Checked
OK, it was working, just that it's timeout per hook, some when you have hundreds of nodes, it's long if you put the test un a "per node hook" 
Updated by Vincent MEMBRÉ over 3 years ago
- Status changed from Pending release to Released
This bug has been fixed in Rudder 6.1.7 which was released today.
Actions