Project

General

Profile

Bug #14331

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

Added by François ARMAND 5 months ago. Updated 3 months 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 - Bug #14333: Remote run should optionnaly honor splay time in async modeNewActions
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)NewActions
Related to Rudder - Bug #14351: On settings page, "Modified files" save button does not become enabled without clicking in the fieldNewActions
Related to Rudder - Bug #14386: UI "settings" for management of hooks works inconsistentlyReleasedActions
Related to Rudder - Architecture #4427: cf-promises check on ALL generated promises leads to huge generation time NewActions
Related to Rudder - Bug #14332: Document hook that trigger an agent run on updateNewActions

Associated revisions

Revision 27c02f5d (diff)
Added by François ARMAND 5 months ago

Fixes #14331: We are forced to wait agent next run before getting a newly generated policy applied

Revision df165e49 (diff)
Added by François ARMAND 5 months ago

fixup! Fixes #14331: We are forced to wait agent next run before getting a newly generated policy applied

Fixes #14331: We are forced to wait agent next run before getting a newly generated policy applied

Revision 0475770a (diff)
Added by François ARMAND 5 months ago

fixup! fixup! Fixes #14331: We are forced to wait agent next run before getting a newly generated policy applied

Fixes #14331: We are forced to wait agent next run before getting a newly generated policy applied

Revision daa38271 (diff)
Added by François ARMAND 5 months ago

Fixes #14331: We are forced to wait agent next run before getting a newly generated policy applied

Revision 3d8e17af
Added by Nicolas CHARLES 5 months ago

Merge pull request #2149 from ncharles/bug_14331/we_are_forced_to_wait_agent_next_run_before_getting_a_newly_generated_policy_applied

Fixes #14331: We are forced to wait agent next run before getting a newly generated policy applied

History

#1

Updated by François ARMAND 5 months ago

  • Status changed from New to In progress
#2

Updated by François ARMAND 5 months 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
#3

Updated by François ARMAND 5 months ago

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

Updated by François ARMAND 5 months 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)

#5

Updated by François ARMAND 5 months ago

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

Updated by Benoît PECCATTE 5 months 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.

#7

Updated by François ARMAND 5 months 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).

#8

Updated by François ARMAND 5 months ago

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

#9

Updated by François ARMAND 5 months 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
#10

Updated by François ARMAND 5 months ago

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

Updated by François ARMAND 5 months ago

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

Updated by François ARMAND 5 months ago

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

Updated by François ARMAND 5 months ago

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

Updated by Rudder Quality Assistant 5 months ago

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

Updated by François ARMAND 5 months ago

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

Updated by Rudder Quality Assistant 5 months ago

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

Updated by Nicolas CHARLES 5 months ago

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

I'm taking over this issue!

#18

Updated by Nicolas CHARLES 5 months 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
#19

Updated by François ARMAND 5 months ago

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

Updated by François ARMAND 5 months ago

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

Updated by François ARMAND 5 months 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
#28

Updated by François ARMAND 5 months ago

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

#29

Updated by François ARMAND 5 months ago

  • Target version changed from 5.0.7 to 5.0.9
#30

Updated by Nicolas CHARLES 5 months 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
#31

Updated by Nicolas CHARLES 5 months ago

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

Updated by Vincent MEMBRÉ 3 months 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
#33

Updated by Vincent MEMBRÉ 3 months ago

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

#34

Updated by Vincent MEMBRÉ 3 months ago

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

Updated by Vincent MEMBRÉ 3 months ago

  • Status changed from Pending release to Released

Also available in: Atom PDF