Actions
Bug #22133
closedBug #22121: Delete action for node is not the correct one because of merge
Parent issue does not address root pb with node deletion config
Pull Request:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
0
Name check:
To do
Fix check:
Checked
Regression:
No
Description
Actually, the merge issue introduced a whole new block, not just changed the value. So we have a duplicated rudder.nodes.delete.defaultMode
declaration, which WILL lead to problems
Updated by François ARMAND about 2 years ago
- Status changed from New to In progress
- Assignee set to François ARMAND
Updated by François ARMAND about 2 years ago
- Status changed from In progress to Pending technical review
- Assignee changed from François ARMAND to Alexis Mousset
- Pull Request set to https://github.com/Normation/rudder/pull/4585
Updated by Anonymous about 2 years ago
- Status changed from Pending technical review to Pending release
Applied in changeset rudder|d946d5e986c2ab5b0f3f8f091df904230e7eb85b.
Updated by François ARMAND about 2 years ago
- Fix check changed from To do to Checked
Updated by Vincent MEMBRÉ about 2 years ago
- Status changed from Pending release to Released
This bug has been fixed in Rudder 7.2.2 which was released today.
Actions