Bug 1764312 - Eventrouter pod in CrashLoopBackOff status: "runtime error: invalid memory address or nil pointer dereference"
Summary: Eventrouter pod in CrashLoopBackOff status: "runtime error: invalid memory ad...
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Logging
Version: 4.1.z
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
: 4.1.z
Assignee: Rich Megginson
QA Contact: Anping Li
Depends On: 1701495 1762409
Blocks: 1764314
TreeView+ depends on / blocked
Reported: 2019-10-22 17:52 UTC by Rich Megginson
Modified: 2020-11-05 21:31 UTC (History)
11 users (show)

Fixed In Version: openshift-ose-logging-eventrouter:v4.1.22-201910250309
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1762409
: 1764314 (view as bug list)
Last Closed: 2020-11-05 21:31:19 UTC
Target Upstream Version:

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2019:3294 0 None None None 2019-11-07 06:33:05 UTC

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.


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