Bug #7086
closed
Promise copy is not convergent: if the copy is interupted, it will never recover
Added by Nicolas CHARLES over 8 years ago.
Updated over 8 years ago.
Category:
System techniques
Description
The copy of promise is a two steps system:
- copy the file containing the timestamp of the last generated promises
- copy the promises if 1 has been repaired
If 2 is somehow interrupted, at the next run 1 will not be done again, and 2 will not start again, resulting in the false belief that promises are correct
1 should be only a check, no real copy, then 2 should be done (2 include also 1)
- Target version changed from 2.10.16 to 2.10.17
- Status changed from New to Pending technical review
- Assignee set to Matthieu CERDA
- Pull Request set to https://github.com/Normation/rudder-techniques/pull/737/files
Francois BAYART wrote:
Nicolas CHARLES wrote:
https://github.com/Normation/rudder-techniques/pull/737/files
is it possible to use it on agent 3.0.6 and 3.1.1 ?
If yes, could you explain the step pleace ?
I'm very interested to test it ;)
To use this commit, you simply have to:
- copy the file techniques/system/common/1.0/update.st of the PR to your rudder server /var/rudder/configuration-repository/techniques/techniques/system/common/1.0/update.st
- in this folder, run git add . && git commit m "Make copy of promise convergent"
On the webapp, go to the Administration/Setting page, and click on "Update techniques now"
- Status changed from Pending technical review to Pending release
- % Done changed from 0 to 100
- Status changed from Pending release to Released
This bug has been fixed in Rudder 2.10.17, 2.11.14, 3.0.9 and 3.1.2 which were released today.
- Related to Bug #7472: Promise copy is not convergent: if the copy is interupted, it will never recover (3.2 branch) added
- Related to Bug #7796: Rudder agent does not detect when promise copy failed added
Also available in: Atom
PDF
Updated by 
Updated by 
Updated by 
Updated by Matthieu CERDA 
Updated by 
Updated by