Actions
Bug #16185
closed
Bug #11917: No compliance from a Rule with only one Directive (from a technique created in the editor) when the Directive is also applied in another Rule
"skipped" directive appears even if directive is not skipped in rule
Status:
Released
Priority:
N/A
Assignee:
Category:
Web - Config management
Target version:
Pull Request:
Severity:
Minor - inconvenience | misleading | easy workaround
UX impact:
User visibility:
Operational - other Techniques | Rudder settings | Plugins
Effort required:
Very Small
Priority:
61
Name check:
Reviewed
Fix check:
Checked
Regression:
Description
Parent ticket #11917 allowed to display a "skipped" directive in the rule when the directive is override in an other rule elsewhere.
But now, the "skipped" directive appears even in the rule where it is applied (see screenshot)
Updated by François ARMAND about 5 years ago
- Status changed from New to In progress
Updated by François ARMAND about 5 years ago
- Status changed from In progress to Pending technical review
- Assignee changed from François ARMAND to Vincent MEMBRÉ
- Pull Request set to https://github.com/Normation/rudder/pull/2598
Updated by François ARMAND about 5 years ago
- Status changed from Pending technical review to Pending release
Applied in changeset rudder|17c27be545ebaaa36b53c94ab9a598b16ebe61bc.
Updated by Alexis Mousset about 5 years ago
- Subject changed from Now, "skipped" directive appears even if directive is not skipped in rule to "skipped" directive appears even if directive is not skipped in rule
- Name check changed from To do to Reviewed
Updated by François ARMAND about 5 years ago
- Fix check changed from To do to Checked
Updated by Vincent MEMBRÉ almost 5 years ago
- Status changed from Pending release to Released
This bug has been fixed in Rudder 5.0.15 which was released today.
Actions