Project

General

Profile

Actions
Copy link

Bug #24488

open

Compliance score is not updated when removing all the policies from a node

Added by Félix DALLIDET 9 months ago. Updated 20 days ago.

Status:
In progress
Priority:
N/A
Assignee:
Elaad FURREEDAN
Category:
Web - Nodes & inventories
Target version:
8.1.11
Pull Request:
Severity:
Minor - inconvenience | misleading | easy workaround
UX impact:
I dislike using that feature
User visibility:
First impressions of Rudder
Effort required:
Priority:
92
Name check:
To do
Fix check:
To do
Regression:
No

Description

It seems to keep a compliance score and even a "trace" of the previous compliance, even if nothing is currently applied on the node.
To reproduce, disable/remove every rule applied to a node and check its compliance score.

I expected the score to be empty (like CVE when not installed) if a node has no policy applied or is in disabled state.

Actions
Copy link
 #1

Updated by Félix DALLIDET 9 months ago

  • Project changed from 92 to Rudder
  • Category set to Web - Nodes & inventories
  • Target version changed from 8.1 to 8.1.0~beta2
Actions
Copy link
 #2

Updated by Vincent MEMBRÉ 9 months ago

  • Target version changed from 8.1.0~beta2 to 8.1.0~rc1
Actions
Copy link
 #3

Updated by Elaad FURREEDAN 9 months ago

  • Status changed from New to In progress
  • Assignee set to Elaad FURREEDAN
Actions
Copy link
 #4

Updated by Vincent MEMBRÉ 9 months ago

  • Target version changed from 8.1.0~rc1 to 8.1.0
Actions
Copy link
 #5

Updated by Vincent MEMBRÉ 9 months ago

  • Target version changed from 8.1.0 to 8.1.1
Actions
Copy link
 #6

Updated by Vincent MEMBRÉ 8 months ago

  • Target version changed from 8.1.1 to 8.1.2
Actions
Copy link
 #7

Updated by Vincent MEMBRÉ 8 months ago

  • Target version changed from 8.1.2 to 8.1.3
Actions
Copy link
 #8

Updated by Vincent MEMBRÉ 7 months ago

  • Target version changed from 8.1.3 to 8.1.4
  • Priority changed from 104 to 102
Actions
Copy link
 #9

Updated by Vincent MEMBRÉ 6 months ago

  • Target version changed from 8.1.4 to 8.1.5
  • Priority changed from 102 to 101
Actions
Copy link
 #10

Updated by Vincent MEMBRÉ 6 months ago

  • Target version changed from 8.1.5 to 8.1.6
  • Priority changed from 101 to 100
Actions
Copy link
 #11

Updated by Vincent MEMBRÉ 5 months ago

  • Target version changed from 8.1.6 to 8.1.7
  • Priority changed from 100 to 99
Actions
Copy link
 #12

Updated by Vincent MEMBRÉ 3 months ago

  • Target version changed from 8.1.7 to 8.1.8
  • Priority changed from 99 to 96
Actions
Copy link
 #13

Updated by Vincent MEMBRÉ about 1 month ago

  • Target version changed from 8.1.8 to 8.1.9
  • Priority changed from 96 to 93
Actions
Copy link
 #14

Updated by Vincent MEMBRÉ 25 days ago

  • Target version changed from 8.1.9 to 8.1.10
  • Priority changed from 93 to 92
Actions
Copy link
 #15

Updated by Vincent MEMBRÉ 20 days ago

  • Target version changed from 8.1.10 to 8.1.11
Actions
Copy link

Also available in: Atom PDF