Bug 1614528 - fluentd crashes if node-config.yaml is missing kubeletArguments
Summary: fluentd crashes if node-config.yaml is missing kubeletArguments
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Logging
Version: 3.11.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: 3.11.0
Assignee: Jeff Cantrill
QA Contact: Anping Li
URL:
Whiteboard:
Depends On:
Blocks: 1616447 1616448
TreeView+ depends on / blocked
 
Reported: 2018-08-09 20:10 UTC by Rich Megginson
Modified: 2021-03-01 08:45 UTC (History)
2 users (show)

Fixed In Version: openshift3/ose-logging-fluentd:v3.11.0-0.19.0.0
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 1616447 1616448 (view as bug list)
Environment:
Last Closed: 2018-10-11 07:24:08 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github openshift origin-aggregated-logging issues 1278 0 None None None 2018-08-09 20:12:00 UTC
Github openshift origin-aggregated-logging pull 1292 0 None None None 2018-08-15 20:39:06 UTC
Red Hat Product Errata RHBA-2018:2652 0 None None None 2018-10-11 07:24:34 UTC

Description Rich Megginson 2018-08-09 20:10:21 UTC 
Description of problem:
https://github.com/openshift/origin-aggregated-logging/issues/1278

The problem is here: https://github.com/openshift/origin-aggregated-logging/blob/master/fluentd/run.sh#L35

The code should check if y['kubeletArguments'] is nil:

        puts (y['kubeletArguments'] || {})['container-runtime-endpoint']")

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


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:
Comment 1 Jeff Cantrill 2018-08-15 20:39:06 UTC 
https://github.com/openshift/origin-aggregated-logging/pull/1292
Comment 3 Anping Li 2018-08-29 10:58:39 UTC 
Move the verified,the ose-logging-fluentd/images/v3.11.0-0.25.0.0 works well when  kubeletArgument missing.
Comment 5 errata-xmlrpc 2018-10-11 07:24:08 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-2018:2652
Note You need to log in before you can comment on or make changes to this bug.