Project

General

Profile

Actions

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 over 5 years ago. Updated 5 months ago.

Status:
New
Priority:
N/A
Category:
Web - Compliance & node report
Target version:
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


Related issues 2 (0 open2 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

Also available in: Atom PDF