Project

General

Profile

Actions
Copy link

Bug #22339

closed

Hook timeout may not have the good value

Added by Vincent MEMBRÉ almost 2 years ago. Updated over 1 year ago.

Status:
Released
Priority:
N/A
Assignee:
François ARMAND
Category:
Web - Config management
Target version:
old 6.2 issues to relocate
Pull Request:
https://github.com/Normation/rudder/p...
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

Related issues 1 (0 open — 1 closed)

Related to Rudder - Bug #18915: We don't know when generation hooks takes more time than expected, massively impacting generation timeReleasedNicolas CHARLESActions
Actions
Copy link

Also available in: Atom PDF