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.
Description
This is not very user friendly.
Updated by François ARMAND almost 6 years ago
- Status changed from New to In progress
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
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
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)
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
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.
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).
Updated by François ARMAND almost 6 years ago
We absolutly need #10623 to be corrected to allow that ticket to work.
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
Updated by François ARMAND almost 6 years ago
- Effort required changed from Very Small to Medium
- Priority changed from 109 to 64
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
Updated by François ARMAND almost 6 years ago
- Assignee changed from François ARMAND to Alexis Mousset
Updated by François ARMAND almost 6 years ago
- Status changed from In progress to Pending technical review
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
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
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
Updated by Nicolas CHARLES over 5 years ago
- Status changed from Discussion to In progress
- Assignee changed from François ARMAND to Nicolas CHARLES
I'm taking over this issue!
Updated by Nicolas CHARLES over 5 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
Updated by François ARMAND over 5 years ago
- Status changed from Pending technical review to Pending release
Applied in changeset rudder|27c02f5d50ac18276b0216c2afc9a6c2dca23407.
Updated by François ARMAND over 5 years ago
Applied in changeset rudder|df165e49ee970ab3e6c46834b3c361141fb31ca3.
Updated by François ARMAND over 5 years ago
Applied in changeset rudder|df165e49ee970ab3e6c46834b3c361141fb31ca3.
Updated by François ARMAND over 5 years ago
Applied in changeset rudder|0475770a994fe55ed831dad03add5b9a7e5d1cb4.
Updated by François ARMAND over 5 years ago
Applied in changeset rudder|0475770a994fe55ed831dad03add5b9a7e5d1cb4.
Updated by François ARMAND over 5 years ago
Applied in changeset rudder|daa3827155b6c310f9b29243f1da56501349908e.
Updated by Nicolas CHARLES over 5 years ago
Applied in changeset rudder|3d8e17af863ab76a3c8f2e704f4045fec21a0b63.
Updated by François ARMAND over 5 years ago
- Related to Bug #14386: UI "settings" for management of hooks works inconsistently added
Updated by François ARMAND over 5 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
Updated by François ARMAND over 5 years ago
This bug has been fixed in Rudder 5.0.7 which was released today.
Updated by François ARMAND over 5 years ago
- Target version changed from 5.0.7 to 5.0.9
Updated by Nicolas CHARLES over 5 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
Updated by Nicolas CHARLES over 5 years ago
- Related to Architecture #4427: cf-promises check on ALL generated promises leads to huge generation time added
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
Updated by Vincent MEMBRÉ over 5 years ago
This bug has been fixed in Rudder 5.0.9 which was released today.
Updated by Vincent MEMBRÉ over 5 years ago
- Related to Bug #14332: Document the hook that triggers an agent run on update added
Updated by Vincent MEMBRÉ over 5 years ago
- Status changed from Pending release to Released