Bug 1834558 - Elasticsearch always logs at trace loglevel
Summary: Elasticsearch always logs at trace loglevel
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Logging
Version: 4.5
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: 4.5.0
Assignee: Jeff Cantrill
QA Contact: Qiaoling Tang
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-05-12 00:23 UTC by Jeff Cantrill
Modified: 2020-07-13 17:37 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: No Doc Update
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-07-13 17:37:35 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github openshift cluster-logging-operator pull 518 0 None closed Bug 1834558: Remove trace loglevel for ES 2021-02-07 09:53:29 UTC
Red Hat Product Errata RHBA-2020:2409 0 None None None 2020-07-13 17:37:48 UTC

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


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