Project

General

Profile

Actions

Bug #22339

closed

Hook timeout may not have the good value

Added by Vincent MEMBRÉ 10 months ago. Updated 4 months ago.

Status:
Released
Priority:
N/A
Category:
Web - Config management
Severity:
UX impact:
User visibility:
Effort required:
Priority:
0
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 open1 closed)

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

Updated by Vincent MEMBRÉ 10 months ago

  • Related to Bug #18915: We don't know when generation hooks takes more time than expected, massively impacting generation time added
Actions #2

Updated by Vincent MEMBRÉ 10 months ago

  • Status changed from New to In progress
  • Assignee set to Vincent MEMBRÉ
Actions #3

Updated by Vincent MEMBRÉ 10 months 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
Actions #4

Updated by Vincent MEMBRÉ 10 months ago

  • Status changed from Pending technical review to Pending release
Actions #5

Updated by François ARMAND 9 months ago

Check that it works as expected in policy generation hooks with defining :

HOOK_WARN_TIMEOUT = 1s
HOOK_KILL_TIMEOUT = 5s

Actions #6

Updated by Alexis Mousset 4 months ago

  • Status changed from Pending release to Released
Actions

Also available in: Atom PDF