Project

General

Profile

Actions
Copy link

Bug #10601

closed

If component value starts with # , report is not outputed by rudder agent output

Added by Nicolas CHARLES over 7 years ago. Updated over 7 years ago.

Status:
Released
Priority:
N/A
Assignee:
Alexis Mousset
Category:
Agent
Target version:
4.0.7
Pull Request:
https://github.com/Normation/rudder-a...
Severity:
Critical - prevents main use of Rudder | no workaround | data loss | security
UX impact:
User visibility:
Operational - other Techniques | Technique editor | Rudder settings
Effort required:
Small
Priority:
67
Name check:
Fix check:
Regression:

Description

If a component value starts with #, the output is not correctly parsed by command rudder agent
Example:

R: @@sshKeyDistribution@@result_success@@uuid@@uuid@@SSH key@@# my key@@2017-04-13 12:31:32+00:00##uuid@#SSH key "# my key" for user was correct

it conflict with the last @#

Related issues 2 (0 open — 2 closed)

Related to Rudder - Bug #8862: Broken agent parsing when some report data start or ends with a separator charRejectedActions
Related to Rudder - Architecture #10648: Use the same regex as rsyslog to parse Rudder reportsRejectedActions
Actions
Copy link

Also available in: Atom PDF