Project

General

Profile

Actions

Bug #26864

open

Node in “keep compliance” displayed as “never ran”

Bug #26864: Node in “keep compliance” displayed as “never ran”

Added by Michel BOUISSOU 10 months ago. Updated 5 days ago.

Status:
New
Priority:
2
Category:
-
Target version:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
0
Name check:
To do
Fix check:
To do
Regression:
No

Description

For some node, currently offline, but in « Keep compliance » node :

- The Rudder server behaviour first was as expected.
- Then at some point it started displaying that the agent « never ran » on this node, showing all compliance in striped blue
- But still showing past compliance and the timestamp of the last report received.

- This looks incoherent.

- Some other offline nodes in « Keep compliance » grace period still display properly, so it's surprising that things seem wrong for a single node only.


Files

Node_keeps_compliance_250503c.png (148 KB) Node_keeps_compliance_250503c.png Compliance still displayed, but blue-striped Michel BOUISSOU, 2025-05-03 13:33
Node_never_ran_250503a.png (50.7 KB) Node_never_ran_250503a.png Node displayed as “never ran” Michel BOUISSOU, 2025-05-03 13:34
zafu_keep_compliance_wrong_250602a.png (59.6 KB) zafu_keep_compliance_wrong_250602a.png Node displayed as having juste reported, it's powered off Michel BOUISSOU, 2025-06-02 07:32
zafu_keep_compliance_wrong_250602b.png (31.4 KB) zafu_keep_compliance_wrong_250602b.png Same node displayed as never reported Michel BOUISSOU, 2025-06-02 07:33
Node_keeps_compliance_250503c.png
Node_never_ran_250503a.png
zafu_keep_compliance_wrong_250602a.png
zafu_keep_compliance_wrong_250602b.png

Related issues 1 (0 open1 closed)

Related to Rudder - Bug #27180: Node compliance persistence fails when all reports from sysevents are cleanedReleasedClark ANDRIANASOLOActions

Updated by Michel BOUISSOU 10 months ago Actions #1

  • File deleted (Node_keeps_compliance_250503b.png)

Updated by Vincent MEMBRÉ 10 months ago Actions #3

  • Target version changed from 8.3.1 to 8.3.2

Updated by François ARMAND 9 months ago Actions #4

  • Assignee set to François ARMAND
  • Priority changed from To review to 2

Hello, does it was just a short time after the last correct report ? Or several days after it ?

Updated by Michel BOUISSOU 9 months ago Actions #5

zafu_keep_compliance_wrong_250602a.png
zafu_keep_compliance_wrong_250602b.png

It can be a short time or several days. “Keep compliance“ mode looks really broken to me, a lot of things display wrong.
In the attached screenshot for example the node both displays as having “never” reported and having srnt its last report a few minutes ago (when it actually has been powered off for 5 days... so it definitely didn't report a few minutes ago).

Powered off nodes get a whole lot of display glitches even red striped “missing reports” or “system policies cound't be applied” when they are just ... offline and all these behaviour seems somewhat random.

Updated by Vincent MEMBRÉ 9 months ago Actions #6

  • Target version changed from 8.3.2 to 8.3.3

Updated by Nicolas CHARLES 8 months ago Actions #7

  • Related to Bug #27180: Node compliance persistence fails when all reports from sysevents are cleaned added

Updated by Félix DALLIDET 7 months ago Actions #8

  • Target version changed from 8.3.3 to 8.3.4

Updated by Vincent MEMBRÉ 5 months ago Actions #9

  • Target version changed from 8.3.4 to 8.3.5

Updated by Vincent MEMBRÉ 5 months ago Actions #10

  • Target version changed from 8.3.5 to 8.3.6

Updated by Vincent MEMBRÉ 3 months ago Actions #11

  • Target version changed from 8.3.6 to 8.3.7

Updated by Vincent MEMBRÉ 2 months ago Actions #12

  • Target version changed from 8.3.7 to 8.3.8

Updated by Vincent MEMBRÉ 2 months ago Actions #13

  • Target version changed from 8.3.8 to 8.3.9

Updated by Vincent MEMBRÉ 5 days ago Actions #14

  • Target version changed from 8.3.9 to 8.3.10
Actions

Also available in: PDF Atom