Actions
Bug #13778
closed
Policy server status is not used to decide if a policy generation is needed
Pull Request:
Severity:
Minor - inconvenience | misleading | easy workaround
UX impact:
User visibility:
Operational - other Techniques | Rudder settings | Plugins
Effort required:
Very Small
Priority:
51
Name check:
Fix check:
Regression:
Description
It seems that if a node becomes a relay, Rudder does not see that a generation is needed.
We need to check if the policy server status is correctly used for node configuration cache (which assess if config changed for the node) and in node info cache (which triggers generation)
Updated by Alexis Mousset about 6 years ago
- Target version set to 5.0-1.2
- Priority changed from 61 to 0
Updated by François ARMAND over 5 years ago
- User visibility changed from Operational - other Techniques | Technique editor | Rudder settings to Operational - other Techniques | Rudder settings | Plugins
- Priority changed from 0 to 57
Updated by Vincent MEMBRÉ about 5 years ago
- Target version changed from 5.0-1.2 to 5.0-1.3
- Priority changed from 57 to 51
Updated by François ARMAND almost 5 years ago
- Status changed from New to Resolved
It's not the case anymore, at least in 6.0.3. Using /opt/rudder/bin/rudder-node-to-relay triggers a generation.
Actions