Actions
Bug #27180
openNode compliance pesistence fails when all reports from sysevents are cleaned
Status:
New
Priority:
2
Assignee:
Category:
Web - Compliance & node report
Target version:
Pull Request:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
0
Name check:
To do
Fix check:
To do
Regression:
No
Description
If we have node compliance that is configured for more than 3 days, and we reached the point where all ruddersysevents are cleaned, then:
- we do have the log message "last node run is too old but compliance persistance is configured for that node for XXX days"
- but the compliance bar in UI remains forever in stipped blue
- and we have "never" in last seen column.
So it seems that when we don't have any runs remaining in ruddersysevent
, then we don't reach "is there compliance" in the UI, BUT we still have the log.
Files
No data to display
Actions