Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1741590

Summary:	remote-syslog error when the record has level=unknown
Product:	OpenShift Container Platform	Reporter:	Rich Megginson <rmeggins>
Component:	Logging	Assignee:	Rich Megginson <rmeggins>
Status:	CLOSED WONTFIX	QA Contact:	Anping Li <anli>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	4.1.0	CC:	anli, aos-bugs, rmeggins
Target Milestone:	---
Target Release:	4.1.z
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
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".	Story Points:	---
Clone Of:	1741585
Clones:	1741591 (view as bug list)		Environment:
Last Closed:	2020-01-20 18:16:33 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:	1741585
Bug Blocks:

Description Rich Megginson 2019-08-15 13:49:45 UTC

+++ This bug was initially created as a clone of Bug #1741585 +++

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-20 10:27:27 UTC

Blocked by https://bugzilla.redhat.com/show_bug.cgi?id=1753936

Comment 4 Rich Megginson 2019-09-20 13:59:07 UTC

(In reply to Anping Li from comment #2)
> Blocked by https://bugzilla.redhat.com/show_bug.cgi?id=1753936

I understand that testing of this bz is blocked by 1753936 but is this bz also failing?  I don't understand why this bz was moved back to ASSIGNED.