Bug #5564
closed
Added by Nicolas CHARLES about 10 years ago.
Updated about 10 years ago.
Category:
System techniques
Description
In #5459, we introduced a mecanism to prevent copy of tools if they were not updated; however it seems there is a problem, as the tools are never copied, nly the update file is copied !
ok, the cause was a poor attempt at optimizing (and I blame myself) don't mixing well with the fact that permissions are correct even at file creation, so it defines the class rudder_tools_updated_kept
Since copy is done only in failsafe (not in normal execution), there is no way (unless hammering manually the failsafe) that multiple copies will occurs of the same files
So the fix is to remove this poor optimization
- Status changed from New to Pending technical review
- Assignee changed from Nicolas CHARLES to Jonathan CLARKE
- Pull Request set to https://github.com/Normation/rudder-techniques/pull/508/files
- Status changed from Pending technical review to Pending release
- % Done changed from 0 to 100
Applied in changeset policy-templates:commit:709f88a8722393d260fd5457e5ea916284eba2c6.
Applied in changeset policy-templates:commit:94b4ebf436b106df74876b3c16e16dd5149b003f.
- Status changed from Pending release to Released
This bug has been fixed in Rudder 2.10.6, which was released today.
Check out:
This bug has been fixed in Rudder 2.10.6, which was released today.
Check out:
Also available in: Atom
PDF
Updated by 
Updated by Jonathan CLARKE 
Updated by Matthieu CERDA