Bug #1991
closed
When a node has not a correct time configuration, the reports are not correct
Description
If a node has a time in the future (resp in the past), the received message have the future timestamp, and thus their is a skew between the displayed reports and the current state of the node.
The solution is not really trivial, but it would help if we knew the message reception time (but it would not be always relevant, for instance if there is a network failure and the message is sent again 30 minutes later ...)
Updated by Jonathan CLARKE almost 13 years ago
- Category set to Web - Compliance & node report
Updated by Jonathan CLARKE over 12 years ago
- Target version set to Ideas (not version specific)
Updated by François ARMAND over 7 years ago
- Description updated (diff)
- Severity set to Minor - inconvenience | misleading | easy workaround
- User visibility set to Getting started - demo | first install | level 1 Techniques
Well, there is technically very little that can be done, and even less if we want to implement an asynchronous reporting system, where the node could send reports only 1 time by day for ex - we will need to believe the timestamp it set.
So the question is more "how can we help a user (especially a new one) to be aware of the importance of time synchronisation between server and node, especially if we are receiving message in the past or in the future".
=> adapt the compliance reports header message for that?
=> had "node time" or similar adjective in technical log table header and other relevant places.
Updated by Jonathan CLARKE over 7 years ago
- Status changed from Discussion to New
- Priority set to 0
Updated by Jonathan CLARKE over 7 years ago
- Status changed from New to Rejected
It is a documented prerequisite for Rudder that all nodes must have correctly configured clocks, and preferably a tight time synchronization using ntp. This bug therefore only concerns a case that will never occur.