Bug 1834558

Summary: Elasticsearch always logs at trace loglevel
Product: OpenShift Container Platform Reporter: Jeff Cantrill <jcantril>
Component: LoggingAssignee: Jeff Cantrill <jcantril>
Status: CLOSED ERRATA QA Contact: Qiaoling Tang <qitang>
Severity: high Docs Contact:
Priority: high    
Version: 4.5CC: aos-bugs, qitang
Target Milestone: ---   
Target Release: 4.5.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: No Doc Update
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-07-13 17:37:35 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Jeff Cantrill 2020-05-12 00:23:05 UTC
Description of problem:

Cluster logging elasticsearch always logs at loglevel trace

Comment 3 Qiaoling Tang 2020-05-13 06:14:03 UTC
Tested with images from 4.5.0-0.ci-2020-05-12-205117, no trace logs, loglevel is debug.

Comment 4 Jeff Cantrill 2020-05-13 12:20:58 UTC
(In reply to Qiaoling Tang from comment #3)
> Tested with images from 4.5.0-0.ci-2020-05-12-205117, no trace logs,
> loglevel is debug.

The loglevel is debug because you set it to debug?  By default it should be info.

Comment 5 Qiaoling Tang 2020-05-13 23:56:01 UTC
No, I didn't set the loglevel.

Comment 6 errata-xmlrpc 2020-07-13 17:37:35 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-2020:2409