User story #5580
closed
Check the monotony of promises generation time on copy to nodes
Added by François ARMAND almost 10 years ago.
Updated over 8 years ago.
Category:
System techniques
Description
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).
- 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
- Status changed from Pending technical review to Discussion
- Assignee changed from Benoît PECCATTE to Nicolas CHARLES
- Target version changed from 140 to 3.0.0~beta1
- Status changed from Discussion to Pending technical review
- Assignee changed from Nicolas CHARLES to Jonathan CLARKE
- Target version changed from 3.0.0~beta1 to 3.1.0~beta1
- Assignee changed from Jonathan CLARKE to Benoît PECCATTE
- Assignee changed from Benoît PECCATTE to Nicolas CHARLES
it's been assigned to me, does it mean I need to update the pr ?
- Target version changed from 3.1.0~beta1 to 3.1.0~rc1
- Target version changed from 3.1.0~rc1 to 3.1.0
- Target version changed from 3.1.0 to 3.1.1
- Target version changed from 3.1.1 to 3.1.2
- Target version changed from 3.1.2 to 3.2.0~beta1
- Assignee changed from Nicolas CHARLES to Jonathan CLARKE
- Pull Request changed from https://github.com/Normation/rudder-techniques/pull/531 to https://github.com/Normation/rudder-techniques/pull/735
- Tracker changed from Bug to User story
- Subject changed from No check is done on the monotony of promises generation time to Check the monotony of promises generation time on copy to nodes
- Status changed from Pending technical review to Pending release
- Status changed from Pending release to Released
This bug has been fixed in Rudder 3.2.0~beta1 which was released today.
- Related to Bug #7796: Rudder agent does not detect when promise copy failed added
Also available in: Atom
PDF