Actions
Bug #24734
closed
Remove System compliance from Score
Status:
Released
Priority:
N/A
Assignee:
Category:
Web - Compliance & node report
Target version:
Pull Request:
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:
0
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
Updated by 
Updated by 
Updated by Anonymous 
Actions