Project

General

Custom queries

Profile

Actions

Bug #14331

closed

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

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

Status:
Released
Priority:
N/A
Category:
Web - Config management
Target version:
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 open3 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
#1

Updated by François ARMAND about 6 years ago

  • Status changed from New to In progress
#2

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

Updated by François ARMAND about 6 years ago

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

Updated by François ARMAND about 6 years ago

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

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

Updated by François ARMAND about 6 years ago

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

Updated by François ARMAND about 6 years 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 about 6 years ago

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

Updated by François ARMAND about 6 years ago

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

Updated by Rudder Quality Assistant about 6 years ago

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

Updated by François ARMAND about 6 years ago

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

Updated by Rudder Quality Assistant about 6 years ago

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

Updated by Nicolas CHARLES about 6 years ago

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

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

Updated by François ARMAND about 6 years ago

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

Updated by François ARMAND about 6 years ago

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

Updated by François ARMAND about 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
#29

Updated by François ARMAND about 6 years ago

  • Target version changed from 5.0.7 to 5.0.9
#30

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

Updated by Nicolas CHARLES about 6 years ago

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

Updated by Vincent MEMBRÉ almost 6 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
#34

Updated by Vincent MEMBRÉ almost 6 years ago

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

Updated by Vincent MEMBRÉ almost 6 years ago

  • Status changed from Pending release to Released
Actions

Also available in: Atom PDF