Actions
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
Pull Request:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
Name check:
Fix check:
Regression:
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
Updated by Nicolas CHARLES over 10 years ago
- 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
Updated by Nicolas CHARLES over 10 years ago
- Status changed from Pending technical review to Pending release
- % Done changed from 0 to 100
Applied in changeset policy-templates:commit:2e65ee2d403a4a53c7544217683206db9cd47772.
Updated by Matthieu CERDA over 10 years ago
Applied in changeset policy-templates:commit:f446cab547a0e3a7835891471eb801f3b95db237.
Updated by Nicolas PERRON over 10 years ago
- 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
Updated by Nicolas PERRON over 10 years ago
- Status changed from Pending release to Released
This bug has been fixed in Rudder 2.6.17, which was released today.
Check out:
- The release announcement: http://www.rudder-project.org/pipermail/rudder-announce/2014-August/000105.html
- The full ChangeLog: http://www.rudder-project.org/foswiki/bin/view/System/Documentation:ChangeLog26
- Download information: https://www.rudder-project.org/site/get-rudder/downloads/
Actions