Actions
Bug #14379
closed
Directive appear in "mixed" mode in a rule applied on only one node
Status:
Released
Priority:
N/A
Assignee:
Category:
Web - Compliance & node report
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:
53
Name check:
Reviewed
Fix check:
Checked
Regression:
Description
I have a case where one rules shows 2 directives in mixed mode - even if it applies to one node (see screenshot)
Files
| mixed.png (27.8 KB) mixed.png | mixed on one rule | ||
| rules-on-multiple.png (38.3 KB) rules-on-multiple.png |
Updated by Nicolas CHARLES almost 6 years ago
- File rules-on-multiple.png rules-on-multiple.png added
reason is : this directives are applied in another rule, with a mixed mode there
see screenshot
Updated by Nicolas CHARLES almost 6 years ago
- Category set to Web - Compliance & node report
Updated by François ARMAND almost 6 years ago
- Target version set to 4.1.21
- Severity set to Major - prevents use of part of Rudder | no simple workaround
- User visibility set to Getting started - demo | first install | Technique editor and level 1 Techniques
- Priority changed from 0 to 70
Updated by François ARMAND almost 6 years ago
- Assignee set to François ARMAND
- Target version changed from 4.1.21 to 4.3.11
- Severity changed from Major - prevents use of part of Rudder | no simple workaround to Minor - inconvenience | misleading | easy workaround
- User visibility changed from Getting started - demo | first install | Technique editor and level 1 Techniques to Operational - other Techniques | Rudder settings | Plugins
- Priority changed from 70 to 32
So, the problem only appears when a directive is used on two rule, and one of the rule dictates the mixed mode, but it does not make sens in the context of the other rule because that rule only apply to homogeneous nodes.
Updated by Vincent MEMBRÉ over 5 years ago
- Target version changed from 4.3.11 to 4.3.12
Updated by Vincent MEMBRÉ over 5 years ago
- Target version changed from 4.3.12 to 4.3.13
Updated by Vincent MEMBRÉ over 5 years ago
- Target version changed from 4.3.13 to 4.3.14
Updated by Vincent MEMBRÉ over 5 years ago
- Target version changed from 4.3.14 to 587
- Priority changed from 32 to 31
Updated by Vincent MEMBRÉ over 5 years ago
- Target version changed from 587 to 4.3.14
Updated by Alexis Mousset over 5 years ago
- Target version changed from 4.3.14 to 5.0.13
Updated by Nicolas CHARLES over 5 years ago
- Related to Bug #15125: Rule shown as "Mixed" whereas applied to one audit node and one (skipped) enforce directive added
Updated by Vincent MEMBRÉ over 5 years ago
- Target version changed from 5.0.13 to 5.0.14
- Priority changed from 31 to 30
Updated by Vincent MEMBRÉ about 5 years ago
- Target version changed from 5.0.14 to 5.0.15
- Priority changed from 30 to 29
Updated by François ARMAND about 5 years ago
- Effort required set to Very Small
- Priority changed from 29 to 54
We should spend a "very small" budget to see if we don't just missed a filter by node at some place.
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 Nicolas CHARLES
- Pull Request set to https://github.com/Normation/rudder/pull/2601
Updated by François ARMAND about 5 years ago
- Status changed from Pending technical review to Pending release
Applied in changeset rudder|3e404fc7459be6e6d255f5aecd468f338e9a2a0e.
Updated by Alexis Mousset about 5 years ago
- 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É about 5 years ago
- Status changed from Pending release to Released
- Priority changed from 54 to 53
This bug has been fixed in Rudder 5.0.15 which was released today.
Actions