Bug #14380
closed
Improve message on Node compliance details when reports are outdated
Added by Nicolas CHARLES about 5 years ago.
Updated about 5 years ago.
Category:
Web - Compliance & node report
Severity:
Major - prevents use of part of Rudder | no simple workaround
User visibility:
Operational - other Techniques | Rudder settings | Plugins
Effort required:
Very Small
Description
A node has out of date policies (4 days old) but it is reassuringly blue, and say that it is expected
This node has recently been assigned a new policy but no reports have been received for the new policy yet.
This is expected, the node is reporting on the previous configuration policy and should report on the new one at latest 2019-02-26 11:04:00. Previous known states are displayed below. The latest reports received for this node are from a run started at 2019-02-26 10:44:00 with configuration ID 20190216-063300-4d41349f.
Current configuration ID for this node is '20190222-161922-28d22b2e' (generated on 2019-02-22 16:19:22).
it should state that it is really too old
happen on Rudder 5.0, most likely in 4.3
Files
- Target version changed from 4.3.10 to 4.3.11
- Severity set to Major - prevents use of part of Rudder | no simple workaround
- User visibility set to Operational - other Techniques | Rudder settings | Plugins
- Effort required set to Very Small
- Priority changed from 0 to 80
So, more information on that one.
It was a conscious choice to always put back in blue a node with an updated policy configuration. One of the reason was that if a node has a big update period, it may be important to know about it.
There is a side effect that we hadn't forseen: in case of frequent updates, a user can miss the fact that the node is mostly grey and never responding.
A easy and satisfying solution could be to just add an other line in the blue message if the last incoming reports are older than the run agent period + grace:
- remove the "This is expected"
- add in the end "which is not expected: please check that the node connection to server is correct".
- Assignee set to François ARMAND
- Status changed from New to In progress
- Status changed from In progress to Pending technical review
- Assignee changed from François ARMAND to Nicolas CHARLES
- Pull Request set to https://github.com/Normation/rudder/pull/2164
- Assignee changed from Nicolas CHARLES to François ARMAND
- Status changed from Pending technical review to Pending release
- Subject changed from Misleading message on node compliance when node has report out of date to Improve message on Node compliance details when reports are outdated
- Status changed from Pending release to Released
This bug has been fixed in Rudder 4.3.11 and 5.0.9 which were released today.
Also available in: Atom
PDF
Updated by 
Updated by 
Updated by 