Bug 1707901
| Summary: | [release-3.9] Fix typo of random_string that prevents forwarding to SYSLOG via UDP to fail | ||
|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Noriko Hosoi <nhosoi> |
| Component: | Logging | Assignee: | Noriko Hosoi <nhosoi> |
| Status: | CLOSED ERRATA | QA Contact: | Anping Li <anli> |
| Severity: | medium | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 3.9.0 | CC: | anli, aos-bugs, jcantril, jmalde, pweil, qitang, rmeggins |
| Target Milestone: | --- | ||
| Target Release: | 3.9.z | ||
| Hardware: | x86_64 | ||
| OS: | All | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: |
Cause:
1) There was a missing '@' for an instance variable in the fleuntd remote syslog plugin code.
2) There were some cases that systemd-journald logged non-decimal facility values.
Consequence:
1) Forwarding logs to remote rsyslog via UDP failed.
2) Forwarding a log record including a non-digital facility value failed regardless of the network protocol.
Fix:
1) The missing '@' was added.
2) The fluentd remote syslog plugin checks the facility value. If the value is not in the defined value set, it resets to the default value.
Result:
Forwarding logs remote rsyslog do not fail.
|
Story Points: | --- |
| Clone Of: | 1707899 | Environment: | |
| Last Closed: | 2019-07-05 06:58:57 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Bug Depends On: | 1703904, 1707899 | ||
| Bug Blocks: | 1707538 | ||
|
Comment 1
Noriko Hosoi
2019-05-08 16:17:16 UTC
Verified in logging-fluentd-v3.9.85-1. Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2019:1642 |