Project

General

Profile

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

Added by Nicolas CHARLES about 8 years ago. Updated about 8 years ago.

Status:
Released
Priority:
N/A
Assignee:
Matthieu CERDA
Category:
Techniques
Target version:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
Regression:

Description

I file didn't change, there may be a no answer.

See #5312 also


Related issues 1 (0 open1 closed)

Related to Rudder - Bug #5312: 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 replacementReleasedMatthieu CERDA2014-07-24Actions
Actions #1

Updated by Nicolas CHARLES about 8 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
Actions #2

Updated by Nicolas CHARLES about 8 years ago

  • Status changed from Pending technical review to Pending release
  • % Done changed from 0 to 100

Applied in changeset policy-templates:commit:01601a231ff6cf711bff1e3a60af83c010998635.

Actions #3

Updated by Matthieu CERDA about 8 years ago

Applied in changeset policy-templates:commit:cfa280c42da7aaf98925711f6398362f4e756e3d.

Actions #4

Updated by Nicolas PERRON about 8 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
Actions #5

Updated by Nicolas PERRON about 8 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:

Actions

Also available in: Atom PDF