Project

General

Profile

Actions
Copy link

Bug #14331

closed

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

Added by François ARMAND almost 6 years ago. Updated over 5 years ago.

Status:
Released
Priority:
N/A
Assignee:
Alexis Mousset
Category:
Web - Config management
Target version:
5.0.9
Pull Request:
https://github.com/Normation/rudder/p...
Severity:
Minor - inconvenience | misleading | easy workaround
UX impact:
User visibility:
First impressions of Rudder
Effort required:
Medium
Priority:
63
Name check:
Fix check:
Regression:

Description

This is not very user friendly.

Related issues 6 (3 open — 3 closed)

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
Copy link
 #1

Updated by François ARMAND almost 6 years ago

  • Status changed from New to In progress
Actions
Copy link
 #2

Updated by François ARMAND almost 6 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
Copy link
 #3

Updated by François ARMAND almost 6 years ago

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

Updated by François ARMAND almost 6 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
Copy link
 #5

Updated by François ARMAND almost 6 years ago

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

Updated by Benoît PECCATTE almost 6 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
Copy link
 #7

Updated by François ARMAND almost 6 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
Copy link
 #8

Updated by François ARMAND almost 6 years ago

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

Actions
Copy link
 #9

Updated by François ARMAND almost 6 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
Copy link
 #10

Updated by François ARMAND almost 6 years ago

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

Updated by François ARMAND almost 6 years ago

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

Updated by François ARMAND almost 6 years ago

  • Assignee changed from François ARMAND to Alexis Mousset
Actions
Copy link
 #13

Updated by François ARMAND almost 6 years ago

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

Updated by Rudder Quality Assistant almost 6 years ago

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

Updated by François ARMAND almost 6 years ago

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

Updated by Rudder Quality Assistant almost 6 years ago

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

Updated by Nicolas CHARLES almost 6 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
Copy link
 #18

Updated by Nicolas CHARLES almost 6 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
Copy link
 #19

Updated by François ARMAND almost 6 years ago

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

Updated by François ARMAND almost 6 years ago

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

Updated by François ARMAND almost 6 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
Copy link
 #28

Updated by François ARMAND almost 6 years ago

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

Actions
Copy link
 #29

Updated by François ARMAND almost 6 years ago

  • Target version changed from 5.0.7 to 5.0.9
Actions
Copy link
 #30

Updated by Nicolas CHARLES almost 6 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
Copy link
 #31

Updated by Nicolas CHARLES almost 6 years ago

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

Updated by Vincent MEMBRÉ over 5 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
Copy link
 #33

Updated by Vincent MEMBRÉ over 5 years ago

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

Actions
Copy link
 #34

Updated by Vincent MEMBRÉ over 5 years ago

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

Updated by Vincent MEMBRÉ over 5 years ago

  • Status changed from Pending release to Released
Actions
Copy link

Also available in: Atom PDF