User story #9353
closed
User story #1808: Add an Audit mode to Rudder: only check properties, no modification on nodes
User story #7219: Add dry-run support to system techniques
User story #9351: Create a dedicated abort report when enforce is used in place of audit
Adapt compliance computing to process abort message
Description
Once we decide what we want to do about the abort message, we need to process it in the compliance.
Message to use, quoted from #9351:
rudder_common_report("Common", "log_info", "&TRACKINGKEY&", "Abort run", "${reason}", "${message}");
with reason being:
unsupported_dryrun
repaired_during_dryrundepending on the cause of the abort.
Updated by Benoît PECCATTE about 8 years ago
- Subject changed from Adapt compliance calcul to process abort message to Adapt compliance computing to process abort message
Updated by François ARMAND about 8 years ago
- Status changed from New to In progress
Updated by François ARMAND about 8 years ago
- Description updated (diff)
Updating description based on messages from #9351
Updated by François ARMAND about 8 years ago
- Status changed from In progress to Pending technical review
- Assignee changed from François ARMAND to Nicolas CHARLES
- Pull Request set to https://github.com/Normation/rudder/pull/1312
Updated by François ARMAND about 8 years ago
- Status changed from Pending technical review to Pending release
- % Done changed from 0 to 100
Applied in changeset rudder|23d0e940458fd1812ef2c62c47a5a4e712853867.
Updated by Vincent MEMBRÉ about 8 years ago
- Target version changed from 4.0.0~rc2 to 4.0.0~rc1
Updated by Alexis Mousset about 8 years ago
- Status changed from Pending release to Released
This bug has been fixed in Rudder 4.0.0 which was released the 10th November 2016.