Bug #22993: Can't deploy, “Configuration state of the object modified by this change request has changed” looping - Change validation - Issue Tracker

Actions

Copy link

Bug #22993

closed

Can't deploy, “Configuration state of the object modified by this change request has changed” looping

Bug #22993: Can't deploy, “Configuration state of the object modified by this change request has changed” looping

Added by Michel BOUISSOU almost 3 years ago. Updated over 2 years ago.

Status:

Released

Priority:

N/A

Assignee:

François ARMAND

Target version:

Rudder plugins - 7.3

Pull Request:

https://github.com/Normation/rudder-p...

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

Effort required:

Priority:

Name check:

To do

Fix check:

Checked

Regression:

Yes

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

Change_validation_cant_deploy_230630a.png (222 KB) Change_validation_cant_deploy_230630a.png

Michel BOUISSOU, 2023-06-30 15:56

Related issues 2 (1 open — 1 closed)

Updated by Michel BOUISSOU almost 3 years ago Actions
Copy link
#1

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.