Actions
Bug #10601
closedIf component value starts with # , report is not outputed by rudder agent output
Pull Request:
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 @#
Updated by Alexis Mousset over 7 years ago
- Related to Bug #8862: Broken agent parsing when some report data start or ends with a separator char added
Updated by Vincent MEMBRÉ over 7 years ago
- Target version changed from 3.1.19 to 3.1.20
Updated by Alexis Mousset over 7 years ago
- 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 over 7 years ago
- Status changed from New to In progress
- Assignee set to Alexis Mousset
Updated by Alexis Mousset over 7 years ago
- 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 over 7 years ago
- Related to Architecture #10648: Use the same regex as rsyslog to parse Rudder reports added
Updated by Alexis Mousset over 7 years ago
- Status changed from Pending technical review to Pending release
Applied in changeset rudder-agent|53d34a94ecb9cb2007105a5deddec740425c4f2a.
Updated by Vincent MEMBRÉ over 7 years ago
- Status changed from Pending release to New
Updated by Nicolas CHARLES over 7 years ago
This was not correctly reverted !
In 4.1 nightly:
BEGIN { FS = "[^@]@#";
Updated by Vincent MEMBRÉ over 7 years ago
- Target version changed from 3.1.20 to 3.1.21
Updated by Vincent MEMBRÉ over 7 years ago
Thiw was revert in 4.0 and 4.1 here : rudder-agent|82f99d4f
Updated by Benoît PECCATTE over 7 years ago
- 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 7 years ago
- Status changed from New to In progress
Updated by Benoît PECCATTE over 7 years ago
- 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 7 years ago
- Status changed from Pending technical review to Pending release
Applied in changeset rudder-agent|3326d01fe3f834d36de6ecbcb493658290102ddd.
Updated by Alexis Mousset over 7 years ago
- Status changed from Pending release to Released
This bug has been fixed in Rudder 4.0.7 which was released today.
- 4.0.7: Announce Changelog
- Download: https://www.rudder-project.org/site/get-rudder/downloads/
Actions