Project

General

Profile

Actions
Copy link

Bug #15140

open

If a component is added to a directive, compliance is not marked in blue as waiting for reports

Added by François ARMAND almost 5 years ago. Updated 2 days ago.

Status:
New
Priority:
N/A
Assignee:
Clark ANDRIANASOLO
Category:
Web - Compliance & node report
Target version:
7.3.15
Pull Request:
Severity:
Minor - inconvenience | misleading | easy workaround
UX impact:
User visibility:
Getting started - demo | first install | Technique editor and level 1 Techniques
Effort required:
Priority:
0
Name check:
To do
Fix check:
To do
Regression:
No

Description

If we have a directive, for example "packages", with two packages, "yum" and "vim" that is already correctly deployed and valid on nodes, and that we had a new package to that directive, after policy regeneration, the directive is completly green on nodes, when we would like to see green 66%, bleu 33%.

The top comment on node compliance details correctly displays that the node configuration is not up to date (see screenshot).

I'm almost sure that ticket was already open previously, but I can't find it.

Files

2019-07-01_11.55.16-Rudder_-_Search_Nodes.png (65 KB) 2019-07-01_11.55.16-Rudder_-_Search_Nodes.png François ARMAND, 2019-07-01 11:56

Related issues 2 (0 open — 2 closed)

Related to Rudder - Bug #15130: New directives don't show up in rules compliance nor in node detailsReleasedFrançois ARMANDActions
Has duplicate Rudder - Bug #18472: Modifying current policies does not create pending status anymoreRejectedClark ANDRIANASOLOActions
Actions
Copy link
 #1

Updated by François ARMAND almost 5 years ago

  • Related to Bug #15130: New directives don't show up in rules compliance nor in node details added
Actions
Copy link
 #2

Updated by Vincent MEMBRÉ almost 5 years ago

  • Target version changed from 5.0.12 to 5.0.13
Actions
Copy link
 #4

Updated by Vincent MEMBRÉ over 4 years ago

  • Target version changed from 5.0.13 to 5.0.14
Actions
Copy link
 #5

Updated by Vincent MEMBRÉ over 4 years ago

  • Target version changed from 5.0.14 to 5.0.15
  • Priority changed from 50 to 49
Actions
Copy link
 #6

Updated by Vincent MEMBRÉ over 4 years ago

  • Target version changed from 5.0.15 to 5.0.16
  • Priority changed from 49 to 47
Actions
Copy link
 #7

Updated by Alexis Mousset about 4 years ago

  • Target version changed from 5.0.16 to 5.0.17
  • Priority changed from 47 to 45
Actions
Copy link
 #8

Updated by Vincent MEMBRÉ about 4 years ago

  • Target version changed from 5.0.17 to 5.0.18
  • Priority changed from 45 to 44
Actions
Copy link
 #9

Updated by Vincent MEMBRÉ almost 4 years ago

  • Target version changed from 5.0.18 to 5.0.19
  • Priority changed from 44 to 42
Actions
Copy link
 #10

Updated by Vincent MEMBRÉ over 3 years ago

  • Target version changed from 5.0.19 to 5.0.20
Actions
Copy link
 #11

Updated by Vincent MEMBRÉ over 3 years ago

  • Target version changed from 5.0.20 to 797
Actions
Copy link
 #12

Updated by Alexis Mousset about 3 years ago

  • Subject changed from If a component is added to a directive, compliance is not marked in bleu as waiting for reports to If a component is added to a directive, compliance is not marked in blue as waiting for reports
Actions
Copy link
 #13

Updated by Benoît PECCATTE almost 3 years ago

  • Target version changed from 797 to 6.1.14
Actions
Copy link
 #14

Updated by Vincent MEMBRÉ almost 3 years ago

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

Updated by Vincent MEMBRÉ almost 3 years ago

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

Updated by Vincent MEMBRÉ over 2 years ago

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

Updated by Vincent MEMBRÉ over 2 years ago

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

Updated by Vincent MEMBRÉ over 2 years ago

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

Updated by Vincent MEMBRÉ about 2 years ago

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

Updated by Vincent MEMBRÉ almost 2 years ago

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

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
 #22

Updated by François ARMAND 7 months ago

  • Related to Bug #18472: Modifying current policies does not create pending status anymore added
Actions
Copy link
 #23

Updated by François ARMAND 6 months ago

  • Target version changed from old 6.1 issues to relocate to 7.3.10
  • Priority changed from 42 to 0
  • Regression set to No

Actually #18472 is a duplicate

Actions
Copy link
 #24

Updated by François ARMAND 6 months ago

  • Assignee set to Clark ANDRIANASOLO
Actions
Copy link
 #25

Updated by François ARMAND 6 months ago

  • Related to deleted (Bug #18472: Modifying current policies does not create pending status anymore)
Actions
Copy link
 #26

Updated by François ARMAND 6 months ago

  • Has duplicate Bug #18472: Modifying current policies does not create pending status anymore added
Actions
Copy link
 #27

Updated by Vincent MEMBRÉ 5 months ago

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

Updated by Vincent MEMBRÉ 3 months ago

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

Updated by Vincent MEMBRÉ about 2 months ago

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

Updated by Vincent MEMBRÉ about 2 months ago

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

Updated by Vincent MEMBRÉ 2 days ago

  • Target version changed from 7.3.14 to 7.3.15
Actions
Copy link

Also available in: Atom PDF