Bug 1616448

Summary:	fluentd crashes if node-config.yaml is missing kubeletArguments
Product:	OpenShift Container Platform	Reporter:	Jeff Cantrill <jcantril>
Component:	Logging	Assignee:	Jeff Cantrill <jcantril>
Status:	CLOSED ERRATA	QA Contact:	Anping Li <anli>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	3.9.0	CC:	anli, aos-bugs, nnosenzo, rmeggins
Target Milestone:	---
Target Release:	3.9.z
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	openshift3/logging-fluentd:v3.9.41-1	Doc Type:	No Doc Update
Doc Text:	undefined	Story Points:	---
Clone Of:	1614528	Environment:
Last Closed:	2018-09-22 04:53:09 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:
Bug Depends On:	1614528
Bug Blocks:	1616447

Description Jeff Cantrill 2018-08-16 00:11:53 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 1 Jeff Cantrill 2018-08-16 00:12:36 UTC

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

Comment 2 Rich Megginson 2018-08-17 18:59:43 UTC

*** Bug 1608688 has been marked as a duplicate of this bug. ***

Comment 4 Anping Li 2018-09-10 09:14:50 UTC

logging-fluentd/images/v3.9.43-1 works without kubeletArguments

Comment 6 errata-xmlrpc 2018-09-22 04:53:09 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:2658