Bug 1836044

Summary:	Lot's of `level=warning msg="Unable to generate log confguraiton: <nil>"` in the CLO pod log.
Product:	OpenShift Container Platform	Reporter:	Qiaoling Tang <qitang>
Component:	Logging	Assignee:	Periklis Tsirakidis <periklis>
Status:	CLOSED ERRATA	QA Contact:	Anping Li <anli>
Severity:	medium	Docs Contact:
Priority:	low
Version:	4.5	CC:	aos-bugs, periklis
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:39:12 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 Qiaoling Tang 2020-05-15 02:22:54 UTC

Description of problem:
There always have lots of `level=warning msg="Unable to generate log confguraiton: <nil>"` in the CLO pod log, for example:

time="2020-05-15T02:10:18Z" level=warning msg="Unable to generate log confguraiton: <nil>"
time="2020-05-15T02:10:18Z" level=info msg="Updating status of Elasticsearch"
time="2020-05-15T02:10:18Z" level=warning msg="Unable to generate log confguraiton: <nil>"
time="2020-05-15T02:10:18Z" level=info msg="Updating status of Fluentd"
time="2020-05-15T02:10:18Z" level=info msg="Updating status of Elasticsearch"
time="2020-05-15T02:10:19Z" level=warning msg="Unable to generate log confguraiton: <nil>"
time="2020-05-15T02:10:19Z" level=info msg="Updating status of Fluentd"
time="2020-05-15T02:10:19Z" level=warning msg="Unable to generate log confguraiton: <nil>"
time="2020-05-15T02:10:19Z" level=info msg="Updating status of Fluentd"
time="2020-05-15T02:10:20Z" level=warning msg="Unable to generate log confguraiton: <nil>"
time="2020-05-15T02:10:21Z" level=info msg="Updating status of Fluentd"
time="2020-05-15T02:10:22Z" level=warning msg="Unable to generate log confguraiton: <nil>"
time="2020-05-15T02:10:22Z" level=info msg="Updating status of Fluentd"
time="2020-05-15T02:10:23Z" level=warning msg="Unable to generate log confguraiton: <nil>"
time="2020-05-15T02:10:48Z" level=info msg="Updating status of Kibana"
time="2020-05-15T02:10:49Z" level=warning msg="Unable to generate log confguraiton: <nil>"
time="2020-05-15T02:10:49Z" level=warning msg="Unable to generate log confguraiton: <nil>"
time="2020-05-15T02:11:19Z" level=info msg="Updating status of Elasticsearch"
time="2020-05-15T02:11:19Z" level=info msg="Updating status of Kibana"
time="2020-05-15T02:11:19Z" level=warning msg="Unable to generate log confguraiton: <nil>"
time="2020-05-15T02:11:19Z" level=warning msg="Unable to generate log confguraiton: <nil>"
time="2020-05-15T02:11:49Z" level=warning msg="Unable to generate log confguraiton: <nil>"
time="2020-05-15T02:12:20Z" level=warning msg="Unable to generate log confguraiton: <nil>"
time="2020-05-15T02:12:50Z" level=warning msg="Unable to generate log confguraiton: <nil>"
time="2020-05-15T02:13:21Z" level=warning msg="Unable to generate log confguraiton: <nil>"
time="2020-05-15T02:13:51Z" level=warning msg="Unable to generate log confguraiton: <nil>"
time="2020-05-15T02:14:21Z" level=warning msg="Unable to generate log confguraiton: <nil>"


Version-Release number of selected component (if applicable):
4.5-2020-05-14-044729

How reproducible:
Always

Steps to Reproduce:
1. deploy logging
2. check CLO pod log
3.

Actual results:


Expected results:


Additional info:

Comment 3 Anping Li 2020-05-31 03:01:58 UTC

No such error in clusterlogging.4.5.0-202005291917

Comment 4 errata-xmlrpc 2020-07-13 17:39:12 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