Actions
Bug #5318
closed
Technique "Enforce a file content" v5.0: post-hook modification reporting is in "No answer" status if the file is correct
Pull Request:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
Name check:
Fix check:
Regression:
Updated by Nicolas CHARLES over 10 years ago
- 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
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:01601a231ff6cf711bff1e3a60af83c010998635.
Updated by Matthieu CERDA over 10 years ago
Applied in changeset policy-templates:commit:cfa280c42da7aaf98925711f6398362f4e756e3d.
Updated by Nicolas PERRON over 10 years ago
- 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
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