Bug #22993
closed
Can't deploy, “Configuration state of the object modified by this change request has changed” looping
Added by Michel BOUISSOU over 1 year ago.
Updated about 1 year ago.
Severity:
Major - prevents use of part of Rudder | no simple workaround
UX impact:
I dislike using that feature
User visibility:
Operational - other Techniques | Rudder settings | Plugins
Description
I can't deploy a directive that goes thru change validation and am stuck in a “Configuration state of the object modified by this change request has changed” loop.
Steps to reproduce :
1/ Enable change validation
2/ Make a change to a directive (i.e. MOTD) requesting validation, without further processing it.
3/ Make another change to the same directive.
4/ Go to CR / Pending review
5/ Reject the 1st request
6/ Accept the 2nd request
7/ Go to CR / Pending deployment
8/ Accept the pending deployment
Results in a loop.
The “diff” displayed by the pending deployment looks like a diff between the current directive and the previous one that was rejected. It's not a diff against the actual current configuration, and I guess that might be part of the issue.
Files
I'm actually confronted with several situations ending in this loop even though I perform a single change, validate the “review” step then the deployment step.
The change may at the sime time be applied and still looping as described above.
In this situation it seems that the stated “Configuration state of the object modified...” corresponds to the change introducted by accepting the deployment request itself.
- Related to Bug #22994: Inconsistency between displayed directive contents and actual deployed configuration added
- UX impact set to I dislike using that feature
- Priority changed from 0 to 100
- Regression changed from No to Yes
- Status changed from New to In progress
- Assignee set to Elaad FURREEDAN
- Status changed from In progress to Pending technical review
- Assignee changed from Elaad FURREEDAN to François ARMAND
- Pull Request set to https://github.com/Normation/rudder-plugins/pull/583
- Status changed from Pending technical review to Pending release
- Priority changed from 100 to 99
- Fix check changed from To do to Checked
- Status changed from Pending release to Released
- Priority changed from 99 to 98
This bug has been fixed in Rudder plugin change-validation v8.0.0.beta1-2.3
- Priority changed from 98 to 97
This bug has been fixed in Rudder plugin change-validation v7.3.6-2.3
- Related to Bug #24111: Pending deployment action are completely messed up added
Also available in: Atom
PDF
Updated by 
Updated by 
Updated by Anonymous 
Updated by 
Updated by 