Bug #5318
closed
Technique "Enforce a file content" v5.0: post-hook modification reporting is in "No answer" status if the file is correct
Added by Nicolas CHARLES over 10 years ago.
Updated over 10 years ago.
Description
I file didn't change, there may be a no answer.
See #5312 also
- Status changed from In progress to Pending technical review
- Assignee changed from Nicolas CHARLES to Matthieu CERDA
- Pull Request set to https://github.com/Normation/rudder-techniques/pull/451
- Status changed from Pending technical review to Pending release
- % Done changed from 0 to 100
Applied in changeset policy-templates:commit:01601a231ff6cf711bff1e3a60af83c010998635.
Applied in changeset policy-templates:commit:cfa280c42da7aaf98925711f6398362f4e756e3d.
- Subject changed from In checkGenericFileContent v5.0, no answer in post modification hook to Technique "Enforce a file content" v5.0: post-hook modification reporting is in "No answer" status if the file is correct
- 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