Bug #27282
open
Node persistant compliance fails after a node has been down for a few days
Description
This is a continuation of bug #27180, which fix didn't actually fix.
After a node (for which a “compliance persistence” propertyu is set for a longer time) has been offline for a few days :
- Its compliance score may turn to “F” ;
- On the nodes list page, it's last run is displayed as “Never” if this column has been added to the display ;
- On the nodes list page, it may get a “warning” icon with a hover hint “Some system policies could not be applied to this node”;
- Even though it correctly gets the little clok icon showing it is in compliance persistence mode.
Plus :
- One node, on its compliance page, displays « The last reports received are from 🕔 2025-07-15 04:18:02+0200 » (which is today), where the node has actually been powered off and thus didn't report for one full week (see attached screenshots for node “nasgul” which last ran on July 6 (correct inventory date), but is displayed as having reported on July 15.
Files
| Nodes_never_250715a.png (185 KB) Nodes_never_250715a.png | Nodes list with “never” and warning sign | ||
| Nodes_never_nasgul_250715b.png (144 KB) Nodes_never_nasgul_250715b.png | Compliance for nasgul node | ||
| Nodes_never_moksha_250715c.png (145 KB) Nodes_never_moksha_250715c.png | Compliance for moksha node | ||
| Nodes_never_zafu_250715d.png (142 KB) Nodes_never_zafu_250715d.png | Compliance for zafu node | ||
| Nodes_never_nasgul_250715e.png (130 KB) Nodes_never_nasgul_250715e.png | Last invnentory receinved on 25/07/06 | ||
| Nodes_never_nasgul_250715f.png (45.2 KB) Nodes_never_nasgul_250715f.png | Wrong : node reported today ??? |
Updated by Michel BOUISSOU about 14 hours ago
- Related to Bug #27180: Node compliance persistence fails when all reports from sysevents are cleaned added
Updated by Félix DALLIDET about 13 hours ago
- Target version changed from 8.3.3 to 8.3.4