Bug #5312
closed
Technique "Enforce a file content" v5.0: post-hook modification reporting is in "Uknown" status if we request a mix of insertion, deletion and/or replacement
Added by Nicolas CHARLES over 10 years ago.
Updated over 10 years ago.
Description
If we mix line insertion, deletion and/or replacement in checkgenericfilecontent, and that we wish to have posthook, we'll have unknown status for posthook
The condition of posthook should be on global state of file, not on each component
- Status changed from New to Pending technical review
- Assignee changed from Nicolas CHARLES to Matthieu CERDA
- Pull Request set to https://github.com/Normation/rudder-techniques/pull/450
- Status changed from Pending technical review to Pending release
- % Done changed from 0 to 100
Applied in changeset policy-templates:commit:2e65ee2d403a4a53c7544217683206db9cd47772.
Applied in changeset policy-templates:commit:f446cab547a0e3a7835891471eb801f3b95db237.
- Subject changed from In checkGenericFileContent v5.0, reporting on post modification hook can be unknown to Technique "Enforce a file content" v5.0: post-hook modification reporting is in "Uknown" status if we request a mix of insertion, deletion and/or replacement
- Status changed from Pending release to Released
This bug has been fixed in Rudder 2.6.17, which was released today.
Check out:
Also available in: Atom
PDF
Updated by 
Updated by Matthieu CERDA 
Updated by Nicolas PERRON