User story #5580closed
Check the monotony of promises generation time on copy to nodes
Today, an agent trying to update its promises is checking promises_generated file to know if they have changed and actually download them.
That file contains the datetime when the promises where generated, but only the hash of the file is check for modifiction, not that the actual datetime is more recent than the current one.
This will be problematic for any topology where a node can have several source for promises and theses sources can be out of sync, with really funny scenario where the node oscillated between several old and new set of promises.
The main idea is to be able to check the content of the file (that will need to contain a timestamp) and see if it's younger than the one in the machine (so that is implying that we need to proceed in two times, but we don't know if these two times are: 1/ download the file, 2/ check its content by comparing with the current one one node and update promises if necessary; OR 1/ download all promises in some directory; and 2/ compare and move promises directories around if necessary).
Updated by Nicolas CHARLES over 6 years ago
- Status changed from New to Pending technical review
- Assignee changed from Nicolas CHARLES to Benoît PECCATTE
- Pull Request set to https://github.com/Normation/rudder-techniques/pull/531
Updated by Nicolas CHARLES over 5 years ago
- Status changed from Pending technical review to Pending release
Applied in changeset rudder-techniques|96eddcb0ffa031ecd6d2afcab47fb0f3145ef3db.
Updated by Jonathan CLARKE over 5 years ago
Applied in changeset rudder-techniques|d8df146d9e605756e73542c4d0817acf881b4da9.