Rudder

If i set the date of a node in the future, then restore it to current time, it will always have no report/unexepected reports until it catches up with the future date

The issue is that we look for the last (in term of date) execution date of this node, in the reportsexecution table, which can be in a distant future if there were desynchronisation

• we can take the last reports before current time (will fail if the node is consistently desynchronized, the behaviour of that exists in 2.11 and before)
• we can modify the table reportsexecution to add when we added the entry in the table (but it is not perfect, as we can have reports arriving out of order given the nature of syslog), and we are dealing with them asynchronously

First solution is easiest to implement, second is a bit more tricky, but none of them are perfect :/