Bug 1707901 - [release-3.9] Fix typo of random_string that prevents forwarding to SYSLOG via UDP to fail
Summary: [release-3.9] Fix typo of random_string that prevents forwarding to SYSLOG vi...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Logging
Version: 3.9.0
Hardware: x86_64
OS: All
unspecified
medium
Target Milestone: ---
: 3.9.z
Assignee: Noriko Hosoi
QA Contact: Anping Li
URL:
Whiteboard:
Depends On: 1703904 1707899
Blocks: 1707538
TreeView+ depends on / blocked
 
Reported: 2019-05-08 16:15 UTC by Noriko Hosoi
Modified: 2019-07-05 06:59 UTC (History)
7 users (show)

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.
Clone Of: 1707899
Environment:
Last Closed: 2019-07-05 06:58:57 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2019:1642 0 None None None 2019-07-05 06:59:13 UTC

Comment 1 Noriko Hosoi 2019-05-08 16:17:16 UTC 
https://github.com/openshift/origin-aggregated-logging/pull/1638
Comment 3 Qiaoling Tang 2019-06-28 06:50:37 UTC 
Verified in logging-fluentd-v3.9.85-1.
Comment 5 errata-xmlrpc 2019-07-05 06:58:57 UTC 
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
Note You need to log in before you can comment on or make changes to this bug.