Project

General

Profile

Actions

Bug #10601

closed

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

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

Added by Nicolas CHARLES almost 9 years ago. Updated over 8 years ago.

Status:
Released
Priority:
N/A
Category:
Agent
Target version:
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 open2 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

Updated by Alexis Mousset almost 9 years ago Actions #1

  • Related to Bug #8862: Broken agent parsing when some report data start or ends with a separator char added

Updated by Vincent MEMBRÉ almost 9 years ago Actions #2

  • Target version changed from 3.1.19 to 3.1.20

Updated by François ARMAND almost 9 years ago Actions #3

  • Priority changed from 0 to 60

Updated by Jonathan CLARKE almost 9 years ago Actions #4

  • Assignee deleted (Alexis Mousset)

Updated by Alexis Mousset almost 9 years ago Actions #5

  • Effort required set to Small
  • Priority changed from 60 to 68

We can try to make a second split instead og change the whole parsing.

Updated by Alexis Mousset almost 9 years ago Actions #6

  • Status changed from New to In progress
  • Assignee set to Alexis Mousset

Updated by Alexis Mousset almost 9 years ago Actions #7

  • Status changed from In progress to Pending technical review
  • Assignee changed from Alexis Mousset to Benoît PECCATTE
  • Pull Request set to https://github.com/Normation/rudder-agent/pull/113

Updated by Alexis Mousset almost 9 years ago Actions #8

Updated by Alexis Mousset almost 9 years ago Actions #9

  • Status changed from Pending technical review to Pending release

Updated by Vincent MEMBRÉ almost 9 years ago Actions #10

  • Status changed from Pending release to New

Updated by Nicolas CHARLES almost 9 years ago Actions #11

This was not correctly reverted !
In 4.1 nightly:

BEGIN {
  FS = "[^@]@#";

Updated by Vincent MEMBRÉ almost 9 years ago Actions #12

  • Target version changed from 3.1.20 to 3.1.21

Updated by Vincent MEMBRÉ over 8 years ago Actions #13

Thiw was revert in 4.0 and 4.1 here : rudder-agent|82f99d4f

Updated by Benoît PECCATTE over 8 years ago Actions #14

  • Target version changed from 3.1.21 to 4.0.7

Let's fix this in 4.0 first

Updated by Benoît PECCATTE over 8 years ago Actions #15

  • Status changed from New to In progress

Updated by Benoît PECCATTE over 8 years ago Actions #16

  • Status changed from In progress to Pending technical review
  • Assignee changed from Benoît PECCATTE to Alexis Mousset
  • Pull Request changed from https://github.com/Normation/rudder-agent/pull/113 to https://github.com/Normation/rudder-agent/pull/116

Updated by Benoît PECCATTE over 8 years ago Actions #17

  • Priority changed from 68 to 67

Updated by Benoît PECCATTE over 8 years ago Actions #18

  • Status changed from Pending technical review to Pending release

Updated by Alexis Mousset over 8 years ago Actions #19

  • Status changed from Pending release to Released

This bug has been fixed in Rudder 4.0.7 which was released today.

Actions

Also available in: PDF Atom