Project

General

Profile

Actions
Copy link

Bug #24843

closed

Rule with all directives skipped does not show in node compliance tree

Added by François ARMAND about 1 year ago. Updated about 1 month ago.

Status:
Resolved
Priority:
N/A
Assignee:
Clark ANDRIANASOLO
Category:
Web - Compliance & node report
Target version:
8.2.6
Pull Request:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
0
Name check:
To do
Fix check:
Checked
Regression:
No

Description

This is the last part of #24097: when a rule has only skipped directives, then it is not displayed at all in the node compliance (ie, the rule is absent in place of being present and containing a list of directives, all skipped).

Files

Download all files
clipboard-202504292158-7p46n.png (122 KB) clipboard-202504292158-7p46n.png François ARMAND, 2025-04-29 21:58
clipboard-202504292159-z6lev.png (93.2 KB) clipboard-202504292159-z6lev.png François ARMAND, 2025-04-29 21:59
clipboard-202504292201-pjfjc.png (152 KB) clipboard-202504292201-pjfjc.png François ARMAND, 2025-04-29 22:01

Related issues 2 (0 open — 2 closed)

Related to Rudder - Bug #24097: Skipped directive does not show in node compliance treeReleasedFrançois ARMANDActions
Related to Rudder - Bug #26712: When directives are skipped, they are multiplied in the directive tab of the ruleReleasedClark ANDRIANASOLOActions
Actions
Copy link
 #1

Updated by François ARMAND about 1 year ago

  • Related to Bug #24097: Skipped directive does not show in node compliance tree added
Actions
Copy link
 #2

Updated by Vincent MEMBRÉ about 1 year ago

  • Target version changed from 8.0.9 to 8.0.10
Actions
Copy link
 #3

Updated by Vincent MEMBRÉ 11 months ago

  • Target version changed from 8.0.10 to 1089
Actions
Copy link
 #4

Updated by Alexis Mousset 11 months ago

  • Target version changed from 1089 to 8.1.6
Actions
Copy link
 #5

Updated by Vincent MEMBRÉ 10 months ago

  • Target version changed from 8.1.6 to 8.1.7
Actions
Copy link
 #6

Updated by Vincent MEMBRÉ 9 months ago

  • Target version changed from 8.1.7 to 8.1.8
Actions
Copy link
 #7

Updated by Vincent MEMBRÉ 7 months ago

  • Target version changed from 8.1.8 to 8.1.9
Actions
Copy link
 #8

Updated by Vincent MEMBRÉ 6 months ago

  • Target version changed from 8.1.9 to 8.1.10
Actions
Copy link
 #9

Updated by Vincent MEMBRÉ 6 months ago

  • Target version changed from 8.1.10 to 8.1.11
Actions
Copy link
 #10

Updated by Vincent MEMBRÉ 5 months ago

  • Target version changed from 8.1.11 to 8.1.12
Actions
Copy link
 #11

Updated by Vincent MEMBRÉ 3 months ago

  • Target version changed from 8.1.12 to 8.1.13
Actions
Copy link
 #12

Updated by François ARMAND about 1 month ago

  • Related to Bug #26712: When directives are skipped, they are multiplied in the directive tab of the rule added
Actions
Copy link
 #13

Updated by François ARMAND about 1 month ago

  • Status changed from New to Resolved

Resolved by #26712 correction: now, a rule with only skipped directive is correctly added in the NodeStatusReport and so, it is correctly displayed everywhere.

Actions
Copy link
 #14

Updated by François ARMAND about 1 month ago

  • Status changed from Resolved to New
  • Target version changed from 8.1.13 to 8.2.6

It seems that even with #26712, I still get the problem.

Actions
Copy link
 #15

Updated by François ARMAND about 1 month ago

  • Status changed from New to Resolved
  • Fix check changed from To do to Checked

OK, so it actually works BUT only after a full generation.
The problem being that since adding only skipped directives doesn't change the expected reports, we are smart and don't change the configId (we stop asap generation for the corresponding node).
We can't do much more beside forcing a generation when there is no changes, which is worse. The next step would be to be able to update the expected reports without changng the configid but still have the correct skipped info. It feels like a big step, not sure worthing it by itself.

Actions
Copy link

Also available in: Atom PDF