Bug 1764312

Summary: Eventrouter pod in CrashLoopBackOff status: "runtime error: invalid memory address or nil pointer dereference"
Product: OpenShift Container Platform Reporter: Rich Megginson <rmeggins>
Component: LoggingAssignee: Rich Megginson <rmeggins>
Status: CLOSED ERRATA QA Contact: Anping Li <anli>
Severity: high Docs Contact:
Priority: high    
Version: 4.1.zCC: anli, aos-bugs, clasohm, david, jcantril, jmalde, nhosoi, qitang, rmeggins, skrenger, sreber
Target Milestone: ---Keywords: Reopened
Target Release: 4.1.z   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: openshift-ose-logging-eventrouter:v4.1.22-201910250309 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: 1762409
: 1764314 (view as bug list) Environment:
Last Closed: 2020-11-05 21:31:19 UTC Type: ---
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: 1701495, 1762409    
Bug Blocks: 1764314    

Comment 4 Anping Li 2019-10-30 07:54:56 UTC
Pass in openshift/ose-logging-eventrouter:v4.1.22-201910291109
The eventroute doesn't crash when type=Info
{"verb":"ADDED","event":{"metadata":{"name":"test-event","namespace":"default","selfLink":"/api/v1/namespaces/default/events/test-event","uid":"136fdbb2-faea-11e9-8c79-0050568bd2a2","resourceVersion":"136850","creationTimestamp":"2019-10-30T07:51:26Z"},"involvedObject":{"kind":"DeploymentConfig","namespace":"default","name":"router","apiVersion":"apps.openshift.io/v1"},"reason":"DeploymentCreated","message":"My test","source":{"component":"deploymentconfig-controller"},"firstTimestamp":null,"lastTimestamp":null,"count":1,"type":"Info"}}

Comment 6 errata-xmlrpc 2019-11-07 06:32:58 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-2019:3294