Actions
Bug #22994
open
Inconsistency between displayed directive contents and actual deployed configuration
Pull Request:
Severity:
Major - prevents use of part of Rudder | no simple workaround
UX impact:
User visibility:
Operational - other Techniques | Rudder settings | Plugins
Effort required:
Priority:
0
Name check:
To do
Fix check:
To do
Regression:
No
Description
It seems that, in the change validation process, if a CR in “Pending review” is accepted, then its deployment is accepted but fails (per bug #22993) we may end up in a situation where when editing the directive again, it contents will display as if the validation process had ultimately succeeded (displays modified contents), when the modification has not been propagated to the configuration distributed to the nodes.
That introduces a persisting inconsistency between the directive contents as displayed on the rudder server, and the actual configuration that is applied onto the nodes.
Updated by Michel BOUISSOU over 1 year ago
- Related to Bug #22993: Can't deploy, “Configuration state of the object modified by this change request has changed” looping added
Actions