Project

General

Profile

Bug #8635

Having a report-separator in the report message causes the report not show up in "rudder agent run" output

Added by Janos Mattyasovszky over 4 years ago. Updated over 4 years ago.

Status:
Released
Priority:
N/A
Category:
Agent
Target version:
Severity:
User visibility:
Effort required:
Priority:

Description

When one has hashmarks in the output, like the very easy case of using NCF Editor => Ensure File Content, and you want to insert a "### This is a comment" to any kind of file, the "rudder agent run" output will not be shown, since I presume the awk-string-splitting does not match on the line because of the hashmarks...

Output of the node's Technical Logs:

Execution Date Severity Rule Directive Component Value Message
2016-07-06 11:44:21 result_na apply my directives to the node NtpTest Service restart ntpd Not applicable was not applicable
2016-07-06 11:44:21 result_success apply my directives to the node NtpTest File enforce content /etc/ntp.conf Insert content ##### ## ## server pool.ntp.org into /etc/ntp.conf was correct
2016-07-06 11:44:21 result_success apply my directives to the node NtpTest Package install ntp Install or update package ntp in version latest was correct

The output of rudder agent run:

Result Technique Component Key Message
success NtpSetup Package install ntp Install or update package ntp in version latest was correct
n/a NtpSetup Service restart ntpd Not applicable was not applicable

The output of rudder agent run -r:

R: @@NtpSetup@@result_success@@b78afdcc-9c9d-4c44-ab52-9653736c426d@@3695598d-7623-46d0-b09a-78bf2232f28e@@32@@Package install@@ntp@@2016-07-06 09:58:32+00:00##6ae57ead-621a-43f0-afb3-29bc27a8ca38@#Install or update package ntp in version latest was correct
R: @@NtpSetup@@result_success@@b78afdcc-9c9d-4c44-ab52-9653736c426d@@3695598d-7623-46d0-b09a-78bf2232f28e@@32@@File enforce content@@/etc/ntp.conf@@2016-07-06 09:58:32+00:00##6ae57ead-621a-43f0-afb3-29bc27a8ca38@#Insert content ##### ## ## server pool.ntp.org into /etc/ntp.conf was correct
R: @@NtpSetup@@result_na@@b78afdcc-9c9d-4c44-ab52-9653736c426d@@3695598d-7623-46d0-b09a-78bf2232f28e@@32@@Service restart@@ntpd@@2016-07-06 09:58:32+00:00##6ae57ead-621a-43f0-afb3-29bc27a8ca38@#Not applicable was not applicable

Found in 3.1.11 (Which is missing from the "Found in version(s)" list.

#1

Updated by Janos Mattyasovszky over 4 years ago

  • Subject changed from Having "#" in reporting does not show up in "rudder agent run" output to Having a report-separator in some NCF Methods causes the report not show up in "rudder agent run" output
#2

Updated by Janos Mattyasovszky over 4 years ago

  • Pull Request set to https://github.com/Normation/rudder-agent/pull/69
#3

Updated by Janos Mattyasovszky over 4 years ago

  • Assignee changed from Nicolas CHARLES to Alexis MOUSSET
#4

Updated by Alexis MOUSSET over 4 years ago

  • Target version set to 3.1.12
#5

Updated by Alexis MOUSSET over 4 years ago

  • Status changed from New to In progress
#6

Updated by Alexis MOUSSET over 4 years ago

  • Status changed from In progress to Pending technical review
  • Assignee changed from Alexis MOUSSET to Benoît PECCATTE
  • Pull Request changed from https://github.com/Normation/rudder-agent/pull/69 to https://github.com/Normation/rudder-agent/pull/70
#7

Updated by Alexis MOUSSET over 4 years ago

  • Assignee changed from Benoît PECCATTE to Nicolas CHARLES
#8

Updated by François ARMAND over 4 years ago

  • Assignee changed from Nicolas CHARLES to Benoît PECCATTE
#9

Updated by Alexis MOUSSET over 4 years ago

  • Assignee changed from Benoît PECCATTE to Nicolas CHARLES
#10

Updated by Anonymous over 4 years ago

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

Updated by Alexis MOUSSET over 4 years ago

  • Subject changed from Having a report-separator in some NCF Methods causes the report not show up in "rudder agent run" output to Having a report-separator in the report message causes the report not show up in "rudder agent run" output
#12

Updated by Alexis MOUSSET over 4 years ago

  • Status changed from Pending release to Released

This bug has been fixed in Rudder 3.1.12 and 3.2.5 which were released today.

Also available in: Atom PDF