Bug #24734: Remove System compliance from Score - Rudder - Issue Tracker

Actions

Copy link

Bug #24734

closed

Remove System compliance from Score

Added by François ARMAND 7 months ago. Updated 7 months ago.

Status:

Released

Priority:

N/A

Assignee:

François ARMAND

Category:

Web - Compliance & node report

Target version:

8.1.1

Pull Request:

https://github.com/Normation/rudder/p...

Severity:

Critical - prevents main use of Rudder | no workaround | data loss | security

UX impact:

User visibility:

Getting started - demo | first install | Technique editor and level 1 Techniques

Effort required:

Priority:

Name check:

To do

Fix check:

Checked

Regression:

Yes

Description

In Rudder 8.0, when we boot and until the first root agent run comes (or if we disable it to make things clearer), we have for root server:

- a summary bar all pending, which don't include system compliance values

- system status all pending, too

If we wait enoung time with the agent disabled, then everything goes in no report.

In Rudder 8.1, we have a regression. After the reboot:

- system status is not applying but success (it should not given no run is available)
- the summary bar looks like it contains sytem status (the part not applying) - or at least, it is not consistant with what is in the details part

Setting to critical since rudder core feature + regression

Files

Download all files

clipboard-202404171354-kqff6.png (160 KB) clipboard-202404171354-kqff6.png		François ARMAND, 2024-04-17 13:54
clipboard-202404171355-4jdk5.png (71.9 KB) clipboard-202404171355-4jdk5.png		François ARMAND, 2024-04-17 13:55
clipboard-202404171356-ysmkl.png (89 KB) clipboard-202404171356-ysmkl.png		François ARMAND, 2024-04-17 13:56
clipboard-202404171402-paqzg.png (179 KB) clipboard-202404171402-paqzg.png		François ARMAND, 2024-04-17 14:02
clipboard-202404171402-erimh.png (101 KB) clipboard-202404171402-erimh.png		François ARMAND, 2024-04-17 14:02
clipboard-202404171402-h8cca.png (81.6 KB) clipboard-202404171402-h8cca.png		François ARMAND, 2024-04-17 14:02
clipboard-202404231151-gbrsc.png (75.5 KB) clipboard-202404231151-gbrsc.png		François ARMAND, 2024-04-23 11:51
clipboard-202404231152-av09p.png (17.7 KB) clipboard-202404231152-av09p.png		François ARMAND, 2024-04-23 11:52
clipboard-202404231152-pm5kj.png (14.4 KB) clipboard-202404231152-pm5kj.png		François ARMAND, 2024-04-23 11:52

Related issues 1 (1 open — 0 closed)

Actions

Copy link

Updated by François ARMAND 7 months ago

So there is likely two bugs:

- the first one is that system compliance is no more going to pending status, and I'm not sure from where it takes a all good value when there's no run (at all) saying so

- the second is that the summary compliance bar provided by compliance score does not filter out system compliance (at least on that case)

Actions

Copy link