Bug 1741585 - remote-syslog error when the record has level=unknown
Summary: remote-syslog error when the record has level=unknown
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Logging
Version: 4.2.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: 4.2.0
Assignee: Rich Megginson
QA Contact: Anping Li
URL:
Whiteboard:
Depends On:
Blocks: 1741590 1741591
TreeView+ depends on / blocked
 
Reported: 2019-08-15 13:40 UTC by Rich Megginson
Modified: 2019-10-16 06:36 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Cause: Logging changed container logs to use log level "unknown" because there is no way to accurately determine container log levels for all types of container logs. See https://bugzilla.redhat.com/show_bug.cgi?id=1726639 Consequence: The remote syslog plugin broke because it does not know how to handle level "unknown" Fix: Change the plugin to use the configured default log level (e.g. "info") when it sees level "unknown". Result: Remote syslog plugin will continue to work and use the default log level instead of "unknown".
Clone Of:
: 1741590 (view as bug list)
Environment:
Last Closed: 2019-10-16 06:36:02 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github openshift origin-aggregated-logging pull 1726 0 None closed Bug 1741585: remote-syslog error when the record has level=unknown 2020-08-04 16:18:05 UTC
Red Hat Product Errata RHBA-2019:2922 0 None None None 2019-10-16 06:36:14 UTC

Description Rich Megginson 2019-08-15 13:40:30 UTC
Description of problem:
We recently switched most container logs to use log level=unknown.  This causes problems for the remote-syslog plugin as `unknown` isn't in the list of levels/severities: 
https://github.com/eric/syslog_protocol/blob/master/lib/syslog_protocol/common.rb#L58

```
2019-08-15 01:00:20 +0000 [warn]: emit transaction failed: error_class=ArgumentError error="'unknown' is not a designated severity" location="/opt/app-root/src/gems/syslog_protocol-0.9.2/lib/syslog_protocol/packet.rb:72:in `severity='" tag="output_ops_tag"
2019-08-15 01:00:20 +0000 [warn]: /opt/app-root/src/gems/syslog_protocol-0.9.2/lib/syslog_protocol/packet.rb:72:in `severity='
```

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 2 Anping Li 2019-09-03 12:46:12 UTC
Using openshift/ose-logging-fluentd/images/v4.2.0-201909020729m the rercord can be forward to remote rsystem via upd/tcp. and there isn't error in the fluentd logs. so Move to verified

Comment 3 errata-xmlrpc 2019-10-16 06:36:02 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:2922


Note You need to log in before you can comment on or make changes to this bug.