Actions
Enhancement #14853
open
If policies are broken on the Rudder Server Root, they won't be repaired until a new policy generation
Added by Nicolas CHARLES over 4 years ago. Updated 13 days ago.
Pull Request:
UX impact:
Suggestion strength:
User visibility:
Operational - other Techniques | Rudder settings | Plugins
Effort required:
Very Small
Regression:
Description
rudder agent check does check for the policy validity
however, it fixes by deleting cache and running failsafe.cf
On a rudder server root, it doesn't do anything as failsafe won't update
Updated by Nicolas CHARLES over 4 years ago
- Related to Bug #14692: Rudder agent check does not repair policies if they are broken added
Updated by Vincent MEMBRÉ over 4 years ago
- Target version changed from 5.0.10 to 5.0.11
Updated by Vincent MEMBRÉ over 4 years ago
- Target version changed from 5.0.11 to 5.0.12
Updated by Vincent MEMBRÉ about 4 years ago
- Target version changed from 5.0.12 to 5.0.13
Updated by Vincent MEMBRÉ about 4 years ago
- Target version changed from 5.0.13 to 5.0.14
Updated by Vincent MEMBRÉ almost 4 years ago
- Target version changed from 5.0.14 to 5.0.15
Updated by Benoît PECCATTE almost 4 years ago
How could a policy be repaired on a root server if not by a policy new generation ?
Updated by Benoît PECCATTE almost 4 years ago
- Effort required set to Very Small
I think the solution is to trigger a new policy generation in this case
Updated by Vincent MEMBRÉ almost 4 years ago
- Target version changed from 5.0.15 to 5.0.16
Updated by Alexis Mousset over 3 years ago
- Target version changed from 5.0.16 to 5.0.17
Updated by Vincent MEMBRÉ over 3 years ago
- Target version changed from 5.0.17 to 5.0.18
Updated by François ARMAND about 3 years ago
- Severity set to Minor - inconvenience | misleading | easy workaround
- User visibility set to Operational - other Techniques | Rudder settings | Plugins
- Priority changed from 0 to 51
Updated by Vincent MEMBRÉ about 3 years ago
- Target version changed from 5.0.18 to 5.0.19
Updated by Vincent MEMBRÉ about 3 years ago
- Target version changed from 5.0.19 to 5.0.20
Updated by Vincent MEMBRÉ almost 3 years ago
- Target version changed from 5.0.20 to 797
Updated by Benoît PECCATTE about 2 years ago
- Target version changed from 797 to 6.1.14
Updated by Vincent MEMBRÉ about 2 years ago
- Target version changed from 6.1.14 to 6.1.15
Updated by Vincent MEMBRÉ about 2 years ago
- Target version changed from 6.1.15 to 6.1.16
Updated by Vincent MEMBRÉ about 2 years ago
- Target version changed from 6.1.16 to 6.1.17
Updated by Vincent MEMBRÉ almost 2 years ago
- Target version changed from 6.1.17 to 6.1.18
Updated by Vincent MEMBRÉ almost 2 years ago
- Target version changed from 6.1.18 to 6.1.19
Updated by François ARMAND over 1 year ago
- Tracker changed from Bug to Enhancement
- Severity deleted (
Minor - inconvenience | misleading | easy workaround) - Priority deleted (
51)
Updated by Vincent MEMBRÉ over 1 year ago
- Target version changed from 6.1.19 to 6.1.20
Updated by Vincent MEMBRÉ over 1 year ago
- Target version changed from 6.1.20 to 6.1.21
Updated by Vincent MEMBRÉ over 1 year ago
- Target version changed from 6.1.21 to old 6.1 issues to relocate
Updated by Alexis Mousset 10 months ago
- Target version changed from old 6.1 issues to relocate to old 6.2 issues to relocate
Updated by Alexis Mousset about 2 months ago
- Target version changed from old 6.2 issues to relocate to 7.2.11
Updated by Vincent MEMBRÉ 13 days ago
- Target version changed from 7.2.11 to 7.2.12
Actions