Project

General

Profile

Actions

Bug #14332

closed

Document the hook that triggers an agent run on update

Added by François ARMAND about 2 years ago. Updated over 1 year ago.

Status:
Released
Priority:
N/A
Category:
Documentation
Target version:
Severity:
Minor - inconvenience | misleading | easy workaround
User visibility:
Operational - other Techniques | Rudder settings | Plugins
Effort required:
Small
Priority:
42

Description

There is some caveat for that hook, they must be documented:

- splay time is not honored,
- agent run each time its configuration is change, which is more frequently than its normal run period (obviously)
- networkd load may be important following a policy generation


Related issues

Related to Rudder - Bug #14331: Trigger agent update and run after policy server has finished policy generationReleasedAlexis MOUSSETActions
Actions #1

Updated by François ARMAND about 2 years ago

  • Parent task changed from #14330 to #14331

Bad parent

Actions #2

Updated by François ARMAND about 2 years ago

  • Target version changed from 5.0.7 to 5.0.9
Actions #3

Updated by Benoît PECCATTE about 2 years ago

  • Severity set to Minor - inconvenience | misleading | easy workaround
  • User visibility set to Operational - other Techniques | Rudder settings | Plugins
  • Priority changed from 0 to 32
Actions #4

Updated by Vincent MEMBRÉ about 2 years ago

  • Target version changed from 5.0.9 to 5.0.10
Actions #5

Updated by Vincent MEMBRÉ about 2 years ago

  • Parent task deleted (#14331)
Actions #6

Updated by Vincent MEMBRÉ about 2 years ago

  • Related to Bug #14331: Trigger agent update and run after policy server has finished policy generation added
Actions #7

Updated by Vincent MEMBRÉ almost 2 years ago

  • Target version changed from 5.0.10 to 5.0.11
  • Priority changed from 32 to 31
Actions #8

Updated by Vincent MEMBRÉ almost 2 years ago

  • Target version changed from 5.0.11 to 5.0.12
Actions #9

Updated by Vincent MEMBRÉ almost 2 years ago

  • Target version changed from 5.0.12 to 5.0.13
Actions #10

Updated by Vincent MEMBRÉ over 1 year ago

  • Target version changed from 5.0.13 to 5.0.14
  • Priority changed from 31 to 30
Actions #11

Updated by Vincent MEMBRÉ over 1 year ago

  • Target version changed from 5.0.14 to 5.0.15
  • Priority changed from 30 to 29
Actions #12

Updated by Benoît PECCATTE over 1 year ago

  • Description updated (diff)
  • Effort required set to Small
  • Priority changed from 29 to 42
Actions #13

Updated by François ARMAND over 1 year ago

  • Status changed from New to In progress
Actions #14

Updated by François ARMAND over 1 year 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/2602
Actions #15

Updated by François ARMAND over 1 year ago

The description in the setting page was already OK, I just changed the part in the hook itself.

Actions #16

Updated by François ARMAND over 1 year ago

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

Updated by Alexis MOUSSET over 1 year ago

  • Subject changed from Document hook that trigger an agent run on update to Document the hook that triggers an agent run on update
Actions #21

Updated by Vincent MEMBRÉ over 1 year ago

  • Status changed from Pending release to Released

This bug has been fixed in Rudder 5.0.15 which was released today.

Actions

Also available in: Atom PDF