Project

General

Profile

Actions
Copy link

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.

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:
97
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)

Related to Change validation - Bug #22994: Inconsistency between displayed directive contents and actual deployed configurationNewActions
Related to Change validation - Bug #24111: Pending deployment action are completely messed upReleasedFrançois ARMANDActions
Actions
Copy link
 #1

Updated by Michel BOUISSOU over 1 year ago

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.

Actions
Copy link
 #2

Updated by Michel BOUISSOU over 1 year ago

  • Related to Bug #22994: Inconsistency between displayed directive contents and actual deployed configuration added
Actions
Copy link
 #3

Updated by Elaad FURREEDAN over 1 year ago

  • UX impact set to I dislike using that feature
  • Priority changed from 0 to 100
  • Regression changed from No to Yes
Actions
Copy link
 #4

Updated by Elaad FURREEDAN over 1 year ago

  • Status changed from New to In progress
  • Assignee set to Elaad FURREEDAN
Actions
Copy link
 #5

Updated by Elaad FURREEDAN over 1 year ago

  • 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
Actions
Copy link
 #6

Updated by Anonymous over 1 year ago

  • Status changed from Pending technical review to Pending release
Actions
Copy link
 #7

Updated by Alexis Mousset over 1 year ago

  • Priority changed from 100 to 99
  • Fix check changed from To do to Checked
Actions
Copy link
 #8

Updated by Vincent MEMBRÉ about 1 year ago

  • 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

Actions
Copy link
 #9

Updated by Vincent MEMBRÉ about 1 year ago

  • Priority changed from 98 to 97

This bug has been fixed in Rudder plugin change-validation v7.3.6-2.3

Actions
Copy link
 #10

Updated by Vincent MEMBRÉ 10 months ago

  • Related to Bug #24111: Pending deployment action are completely messed up added
Actions
Copy link

Also available in: Atom PDF