Bug #5208
closed
Technique "Enforce a file content": post-hook modification reporting is in "No answer" status if we enforce the content of the file only at creation
Added by Nicolas CHARLES over 10 years ago.
Updated over 10 years ago.
Description
If we enforce only at creation the content of the file, the post modification hook has the "No Reports" status once the file has been created
- Status changed from New to Pending technical review
- Assignee set to Jonathan CLARKE
- Pull Request set to https://github.com/Normation/rudder-techniques/pull/436
- Status changed from Pending technical review to Pending release
- % Done changed from 0 to 100
Applied in changeset policy-templates:commit:57888fa1724f4ef04e65b756ec3100032a2df66a.
Applied in changeset policy-templates:commit:5c3f2466520d2364edec100ffb06d8fbc09d24f6.
- Subject changed from CheckGenericFileContent has No Report status for post modification hook when we enforce the content of the file only at creation to CheckGenericFileContent does not send reports for post modification hook when we enforce the content of the file only at creatio
- Subject changed from CheckGenericFileContent does not send reports for post modification hook when we enforce the content of the file only at creatio to Technique "Enforce a file content": post-hook modification reporting is in "No answer" status if we enforce the content of the file only at creation
- 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 Jonathan CLARKE 
Updated by 
Updated by Nicolas PERRON