Project

General

Profile

Actions

Bug #14331

closed

Trigger agent update and run after policy server has finished policy generation

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

Status:
Released
Priority:
N/A
Category:
Web - Config management
Target version:
Severity:
Minor - inconvenience | misleading | easy workaround
User visibility:
First impressions of Rudder
Effort required:
Medium
Priority:
63

Description

This is not very user friendly.


Related issues

Related to Rudder - User story #14333: Remote run should optionnaly honor splay time in async modeNewFrançois ARMANDActions
Related to Rudder - Bug #10623: Hooks content/permissions are changed during Rudder upgrade (for ex /opt/rudder/etc/hooks.d/policy-generation-node-ready/10-cf-promise-check is replaced)ReleasedAlexis MOUSSETActions
Related to Rudder - Bug #14351: On settings page, "Modified files" save button does not become enabled without clicking in the fieldNewRaphael GAUTHIERActions
Related to Rudder - Bug #14386: UI "settings" for management of hooks works inconsistentlyReleasedFrançois ARMANDActions
Related to Rudder - Architecture #4427: cf-promises check on ALL generated promises leads to huge generation time NewNicolas CHARLESActions
Related to Rudder - Bug #14332: Document the hook that triggers an agent run on updateReleasedNicolas CHARLESActions
Actions #1

Updated by François ARMAND about 2 years ago

  • Status changed from New to In progress
Actions #2

Updated by François ARMAND about 2 years ago

  • Status changed from In progress to Pending technical review
  • Assignee changed from François ARMAND to Alexis MOUSSET
  • Pull Request set to https://github.com/Normation/rudder/pull/2141
Actions #3

Updated by François ARMAND about 2 years ago

  • Related to User story #14333: Remote run should optionnaly honor splay time in async mode added
Actions #4

Updated by François ARMAND about 2 years ago

As this is a big behavior change, we must:

- not do it automatically on upgrade (only new installation get it),
- add a setting in Rudder UI to manage it (so that user can change it easely),
- limit the max number of node on which the change is done, configurable along with the setting (or fraction of the impacted nodes)

Actions #5

Updated by François ARMAND about 2 years ago

  • Status changed from Pending technical review to In progress
  • Assignee changed from Alexis MOUSSET to François ARMAND
Actions #6

Updated by Benoît PECCATTE about 2 years ago

Applying randomly on node with a maximum number might be hard to understand for the user who would like to check where it has been applied.

Actions #7

Updated by François ARMAND about 2 years ago

Benoît PECCATTE wrote:

Applying randomly on node with a maximum number might be hard to understand for the user who would like to check where it has been applied.

Yes, but for now we can't communicate that to the user appart in logs (which is not very usefull for your objection).

Actions #8

Updated by François ARMAND about 2 years ago

We absolutly need #10623 to be corrected to allow that ticket to work.

Actions #9

Updated by François ARMAND about 2 years ago

  • Related to Bug #10623: Hooks content/permissions are changed during Rudder upgrade (for ex /opt/rudder/etc/hooks.d/policy-generation-node-ready/10-cf-promise-check is replaced) added
Actions #10

Updated by François ARMAND about 2 years ago

  • Effort required changed from Very Small to Medium
  • Priority changed from 109 to 64
Actions #11

Updated by François ARMAND about 2 years ago

  • Related to Bug #14351: On settings page, "Modified files" save button does not become enabled without clicking in the field added
Actions #12

Updated by François ARMAND about 2 years ago

  • Assignee changed from François ARMAND to Alexis MOUSSET
Actions #13

Updated by François ARMAND about 2 years ago

  • Status changed from In progress to Pending technical review
Actions #14

Updated by Rudder Quality Assistant about 2 years ago

  • Status changed from Pending technical review to Discussion
  • Assignee changed from Alexis MOUSSET to François ARMAND
Actions #15

Updated by François ARMAND about 2 years ago

  • Status changed from Discussion to Pending technical review
  • Assignee changed from François ARMAND to Alexis MOUSSET
Actions #16

Updated by Rudder Quality Assistant about 2 years ago

  • Status changed from Pending technical review to Discussion
  • Assignee changed from Alexis MOUSSET to François ARMAND
Actions #17

Updated by Nicolas CHARLES about 2 years ago

  • Status changed from Discussion to In progress
  • Assignee changed from François ARMAND to Nicolas CHARLES

I'm taking over this issue!

Actions #18

Updated by Nicolas CHARLES about 2 years ago

  • Status changed from In progress to Pending technical review
  • Assignee changed from Nicolas CHARLES to Alexis MOUSSET
  • Pull Request changed from https://github.com/Normation/rudder/pull/2141 to https://github.com/Normation/rudder/pull/2149
Actions #19

Updated by François ARMAND about 2 years ago

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

Updated by François ARMAND about 2 years ago

  • Related to Bug #14386: UI "settings" for management of hooks works inconsistently added
Actions #27

Updated by François ARMAND about 2 years ago

  • Subject changed from We are forced to wait agent next run before getting a newly generated policy applied to Add an optional hook to trigger node update on nodes with new policies
Actions #28

Updated by François ARMAND about 2 years ago

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

Actions #29

Updated by François ARMAND about 2 years ago

  • Target version changed from 5.0.7 to 5.0.9
Actions #30

Updated by Nicolas CHARLES about 2 years ago

  • Subject changed from Add an optional hook to trigger node update on nodes with new policies to Add an optional hook to trigger node update on nodes with new policies and add possibility to allow/disallow generated policy validation
Actions #31

Updated by Nicolas CHARLES about 2 years ago

  • Related to Architecture #4427: cf-promises check on ALL generated promises leads to huge generation time added
Actions #32

Updated by Vincent MEMBRÉ about 2 years ago

  • Subject changed from Add an optional hook to trigger node update on nodes with new policies and add possibility to allow/disallow generated policy validation to Trigger agent update and run after policy server has finished policy generation
  • Priority changed from 64 to 63
Actions #33

Updated by Vincent MEMBRÉ about 2 years ago

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

Actions #34

Updated by Vincent MEMBRÉ about 2 years ago

  • Related to Bug #14332: Document the hook that triggers an agent run on update added
Actions #35

Updated by Vincent MEMBRÉ about 2 years ago

  • Status changed from Pending release to Released
Actions

Also available in: Atom PDF