Actions
Bug #22178
closedCannot deploy changes on a group where properties are defined with a validated user
Status:
Released
Priority:
N/A
Assignee:
Category:
Web - Config management
Target version:
Pull Request:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
0
Name check:
To do
Fix check:
Checked
Regression:
No
Description
If you try to modify a group with change validation plugin with a validated user, and this group has properties, the change will be refused because it thinks the group has changed.
It's because the comparison between properties is not correct (need to sort by name and remoe providers ...)
Updated by Vincent MEMBRÉ about 2 years ago
- Status changed from New to In progress
- Assignee set to Vincent MEMBRÉ
Updated by Vincent MEMBRÉ about 2 years ago
- Status changed from In progress to Pending technical review
- Assignee changed from Vincent MEMBRÉ to François ARMAND
- Pull Request set to https://github.com/Normation/rudder/pull/4602
Updated by Vincent MEMBRÉ about 2 years ago
- Status changed from Pending technical review to Pending release
Applied in changeset rudder|d441c8a9bd6047ac80f297237541065a11099af1.
Updated by Nicolas CHARLES almost 2 years ago
- Fix check changed from To do to Checked
Updated by Alexis Mousset almost 2 years ago
- Status changed from Pending release to Released
This bug has been fixed in Rudder 7.1.9 and 7.2.3 which were released today.
Actions