Actions
Bug #10643
closed
If node run interval is longer than 5 minutes, there may be "no report" at start of Rudder
Pull Request:
Severity:
Major - prevents use of part of Rudder | no simple workaround
UX impact:
User visibility:
Operational - other Techniques | Technique editor | Rudder settings
Effort required:
Priority:
0
Name check:
Fix check:
Regression:
Description
I restarted the web interface, and got a lot of node in no answer, with message
No recent reports have been received for this node in the grace period since the last configuration policy change. This is unexpected. Please check the status of the agent by running 'rudder agent health' on the node. For information, expected node policies are displayed below. Current configuration ID for this node is '20170424-130636-20b8d2eb' (generated on 2017-04-24 13:06:36).
Previous run was a 13:13, and current run was 13:23 (and it was 13:23). It solved itself, but it seems we are missing some runs at start
Happens in 4.1, may happen in earlier version
Updated by 
Updated by 
Updated by 
Updated by 
Updated by
Actions