Actions
Bug #14995
open
When node configuration is updated, status becomes pending even if the node is sending very old reports
Pull Request:
Severity:
Major - prevents use of part of Rudder | no simple workaround
UX impact:
User visibility:
Operational - other Techniques | Rudder settings | Plugins
Effort required:
Small
Priority:
0
Name check:
Fix check:
Regression:
No
Description
One node sends reports from a configuration dating 15:22
Several policy generation happened in a row since, and i get following status
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-05-30 19:34:06. Previous known states are displayed below. The latest reports received for this node are from a run started at 2019-05-30 19:24:06 with configuration ID 20190529-155230-4fa56379. Current configuration ID for this node is '20190530-191237-a0dac60d' (generated on 2019-05-30 19:12:37).
Every time, the "should report on the latest one" is in 10 minutes.
Since the node is still sending reports for a configuration that is very old, Rudder should know that it is not updating its configuration, and so Rudder should not say "pending", but "error".
Files
Updated by 
Updated by 
Updated by 
Updated by 
Updated by 
Actions