Bug 1616447 - 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.10.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: 3.10.z
Assignee: Jeff Cantrill
QA Contact: Anping Li
URL:
Whiteboard:
Depends On: 1614528 1616448
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-08-16 00:10 UTC by Jeff Cantrill
Modified: 2021-03-01 08:38 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: No Doc Update
Doc Text:
undefined
Clone Of: 1614528
Environment:
Last Closed: 2018-08-31 06:18:11 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-16 00:10:28 UTC
Github openshift origin-aggregated-logging pull 1292 0 None None None 2018-08-16 00:10:28 UTC
Red Hat Product Errata RHBA-2018:2376 0 None None None 2018-08-31 06:18:22 UTC

Description Jeff Cantrill 2018-08-16 00:10:28 UTC
+++ This bug was initially created as a clone of Bug #1614528 +++

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:

--- Additional comment from Jeff Cantrill on 2018-08-15 16:39:06 EDT ---

https://github.com/openshift/origin-aggregated-logging/pull/1292

Comment 3 Anping Li 2018-08-23 10:56:43 UTC
It fix in logging:v3.10.34.

Comment 5 errata-xmlrpc 2018-08-31 06:18:11 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:2376


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