Project

General

Profile

Actions
Copy link

Bug #15125

open

Rule shown as "Mixed" whereas applied to one audit node and one (skipped) enforce directive

Added by Benoît PECCATTE almost 5 years ago. Updated about 9 hours ago.

Status:
New
Priority:
N/A
Assignee:
-
Category:
Web - Compliance & node report
Target version:
7.3.15
Pull Request:
Severity:
Minor - inconvenience | misleading | easy workaround
UX impact:
User visibility:
Infrequent - complex configurations | third party integrations
Effort required:
Medium
Priority:
0
Name check:
To do
Fix check:
To do
Regression:
No

Description

Found in 5.0.1

Files

Download all files
bug_tag3.png (6.53 KB) bug_tag3.png Benoît PECCATTE, 2019-06-26 09:59
bug_tag4.png (18.7 KB) bug_tag4.png Benoît PECCATTE, 2019-06-26 09:59
clipboard-202311091717-qhzn0.png (82.2 KB) clipboard-202311091717-qhzn0.png François ARMAND, 2023-11-09 17:17

Related issues 3 (1 open — 2 closed)

Related to Rudder - Bug #15124: Rule tag is "Enforce" whereas it has both enforce and audit nodesReleasedNicolas CHARLESActions
Related to Rudder - Bug #14379: Directive appear in "mixed" mode in a rule applied on only one nodeReleasedNicolas CHARLESActions
Related to Rudder - Bug #22525: Directives applied twice don't show in rule details (they should be skipped)Pending releaseElaad FURREEDANActions
Actions
Copy link
 #1

Updated by Nicolas CHARLES almost 5 years ago

  • Target version set to 5.0.13
Actions
Copy link
 #2

Updated by Nicolas CHARLES almost 5 years ago

  • Related to Bug #15124: Rule tag is "Enforce" whereas it has both enforce and audit nodes added
Actions
Copy link
 #3

Updated by Nicolas CHARLES almost 5 years ago

  • Related to Bug #14379: Directive appear in "mixed" mode in a rule applied on only one node added
Actions
Copy link
 #4

Updated by François ARMAND almost 5 years ago

  • Subject changed from Rule shown as "Mixed" whereas is is applied olnly to one audit node to Rule shown as "Mixed" whereas is is applied only to one audit node
  • 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
Actions
Copy link
 #5

Updated by Vincent MEMBRÉ over 4 years ago

  • Target version changed from 5.0.13 to 5.0.14
  • Priority changed from 70 to 68
Actions
Copy link
 #6

Updated by Vincent MEMBRÉ over 4 years ago

  • Target version changed from 5.0.14 to 5.0.15
  • Priority changed from 68 to 67
Actions
Copy link
 #7

Updated by François ARMAND over 4 years ago

  • Effort required set to Very Small
  • Priority changed from 67 to 93

Perhaps a missing filter by node, we should at least try to understand the pb in a budget of "very small"

Actions
Copy link
 #8

Updated by Vincent MEMBRÉ over 4 years ago

  • Target version changed from 5.0.15 to 5.0.16
  • Priority changed from 93 to 92
Actions
Copy link
 #9

Updated by Alexis Mousset about 4 years ago

  • Target version changed from 5.0.16 to 5.0.17
  • Priority changed from 92 to 88
Actions
Copy link
 #10

Updated by Vincent MEMBRÉ about 4 years ago

  • Target version changed from 5.0.17 to 5.0.18
  • Priority changed from 88 to 85
Actions
Copy link
 #11

Updated by Nicolas CHARLES almost 4 years ago

  • Assignee set to Benoît PECCATTE
  • Target version changed from 5.0.18 to 6.0.8
  • Priority changed from 85 to 82

Many things changed since 5.0.1, so retargeting to 6.0 and we first need to try to reproduce it

Actions
Copy link
 #12

Updated by Nicolas CHARLES almost 4 years ago

  • Effort required changed from Very Small to Small
  • Priority changed from 82 to 71

This still happens in 6.0 - this is because there is One directive in Audit, and 2 directives skipped, and one of them is in Enforce
So we need to be able to identify that some directives are skipped in the computation of Enforce/Audit/Mixed

probably larger than very small

Actions
Copy link
 #13

Updated by Nicolas CHARLES almost 4 years ago

  • Effort required changed from Small to Medium
  • Priority changed from 71 to 44
Actions
Copy link
 #14

Updated by Vincent MEMBRÉ almost 4 years ago

  • Target version changed from 6.0.8 to 6.0.9
Actions
Copy link
 #15

Updated by Vincent MEMBRÉ over 3 years ago

  • Target version changed from 6.0.9 to 6.0.10
Actions
Copy link
 #16

Updated by Vincent MEMBRÉ over 3 years ago

  • Target version changed from 6.0.10 to 798
Actions
Copy link
 #17

Updated by Alexis Mousset almost 3 years ago

  • Target version changed from 798 to 6.1.14
Actions
Copy link
 #18

Updated by Vincent MEMBRÉ almost 3 years ago

  • Target version changed from 6.1.14 to 6.1.15
Actions
Copy link
 #19

Updated by Vincent MEMBRÉ almost 3 years ago

  • Target version changed from 6.1.15 to 6.1.16
Actions
Copy link
 #20

Updated by Vincent MEMBRÉ over 2 years ago

  • Target version changed from 6.1.16 to 6.1.17
Actions
Copy link
 #21

Updated by Vincent MEMBRÉ over 2 years ago

  • Target version changed from 6.1.17 to 6.1.18
Actions
Copy link
 #22

Updated by Vincent MEMBRÉ over 2 years ago

  • Target version changed from 6.1.18 to 6.1.19
Actions
Copy link
 #23

Updated by Vincent MEMBRÉ about 2 years ago

  • Target version changed from 6.1.19 to 6.1.20
Actions
Copy link
 #24

Updated by Vincent MEMBRÉ almost 2 years ago

  • Target version changed from 6.1.20 to 6.1.21
Actions
Copy link
 #25

Updated by Vincent MEMBRÉ almost 2 years ago

  • Target version changed from 6.1.21 to old 6.1 issues to relocate
Actions
Copy link
 #26

Updated by Benoît PECCATTE about 1 year ago

  • Assignee deleted (Benoît PECCATTE)
  • Priority changed from 44 to 0
  • Regression set to No
Actions
Copy link
 #27

Updated by François ARMAND 6 months ago

  • Subject changed from Rule shown as "Mixed" whereas is is applied only to one audit node to Rule shown as "Mixed" whereas applied to one audit node and one (skipped) enforce directive

It is still the case as of 7.3.9, but the main problem is that "skipped" directive are not displayed, when they really should.

Correcting #22525 will help with that one (and then, I'm not sure we want to change the behavior of mixed without making a clear distinction between "what is the status of the applied directive to the rule (ie compliance)" and "what is the status of the configured directive for the rule" (where "mixed" is correct)

Actions
Copy link
 #28

Updated by François ARMAND 6 months ago

  • File clipboard-202311091717-qhzn0.png clipboard-202311091717-qhzn0.png added
  • Target version changed from old 6.1 issues to relocate to 7.3.10
  • 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 Infrequent - complex configurations | third party integrations

Actions
Copy link
 #29

Updated by François ARMAND 6 months ago

  • Related to Bug #22525: Directives applied twice don't show in rule details (they should be skipped) added
Actions
Copy link
 #30

Updated by Vincent MEMBRÉ 4 months ago

  • Target version changed from 7.3.10 to 7.3.11
Actions
Copy link
 #31

Updated by Vincent MEMBRÉ 3 months ago

  • Target version changed from 7.3.11 to 7.3.12
Actions
Copy link
 #32

Updated by Vincent MEMBRÉ about 2 months ago

  • Target version changed from 7.3.12 to 7.3.13
Actions
Copy link
 #33

Updated by Vincent MEMBRÉ about 2 months ago

  • Target version changed from 7.3.13 to 7.3.14
Actions
Copy link
 #34

Updated by Vincent MEMBRÉ about 9 hours ago

  • Target version changed from 7.3.14 to 7.3.15
Actions
Copy link

Also available in: Atom PDF