Bug 1591158

Summary:	[3.9][crio] Event process failure error appears in atomic-openshift-node log
Product:	OpenShift Container Platform	Reporter:	Meng Bo <bmeng>
Component:	Containers	Assignee:	Antonio Murdaca <amurdaca>
Status:	CLOSED ERRATA	QA Contact:	weiwei jiang <wjiang>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	3.9.0	CC:	amurdaca, aos-bugs, bmeng, dwalsh, jhonce, jokerman, mmccomas, mpatel
Target Milestone:	---
Target Release:	3.9.z
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:	1591118	Environment:
Last Closed:	2019-04-09 14:20:17 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:	1591118
Bug Blocks:

Description Meng Bo 2018-06-14 07:58:42 UTC

+++ This bug was initially created as a clone of Bug #1591118 +++

Description of problem:
Tons of "invalid character 'c' looking for beginning of value" errors appear in node log when cluster running with crio.

Jun 13 23:58:12 ip-172-18-14-79.ec2.internal atomic-openshift-node[18924]: ERROR: logging before flag.Parse: W0613 23:58:12.971203   18924 manager.go:1178] Failed to process watch event {EventType:0 Name:/kubepods.slice/kubepods-besteffort.slice/kubepods-besteffort-pod2262d6c2_6f87_11e8_86dd_0eb037b2774e.slice/crio-b188fba45a612b6fd7cbb00dd6150e182e86ecef6f0447abd67210f08e2a456f.scope WatchSource:0}: invalid character 'c' looking for beginning of value
Jun 13 23:58:16 ip-172-18-14-79.ec2.internal atomic-openshift-node[18924]: ERROR: logging before flag.Parse: W0613 23:58:16.489277   18924 manager.go:1178] Failed to process watch event {EventType:0 Name:/kubepods.slice/kubepods-besteffort.slice/kubepods-besteffort-pod2262d6c2_6f87_11e8_86dd_0eb037b2774e.slice/crio-2cb7f38521db0cd9584b4d52c7d5e76e39aea96f226b7f4fadf811252e3c5e5a.scope WatchSource:0}: invalid character 'c' looking for beginning of value
Jun 13 23:59:40 ip-172-18-14-79.ec2.internal atomic-openshift-node[18924]: ERROR: logging before flag.Parse: W0613 23:59:40.225422   18924 manager.go:1178] Failed to process watch event {EventType:0 Name:/kubepods.slice/kubepods-besteffort.slice/kubepods-besteffort-pod5b7ccb19_6f87_11e8_86dd_0eb037b2774e.slice/crio-e6ccc38071c3b403accd153c11775f7fd933305f31b551d4b6c6597692ce777d.scope WatchSource:0}: invalid character 'c' looking for beginning of value
Jun 13 23:59:54 ip-172-18-14-79.ec2.internal atomic-openshift-node[18924]: ERROR: logging before flag.Parse: W0613 23:59:54.687828   18924 manager.go:1178] Failed to process watch event {EventType:0 Name:/kubepods.slice/kubepods-besteffort.slice/kubepods-besteffort-pod5b7ccb19_6f87_11e8_86dd_0eb037b2774e.slice/crio-ea3d01c5538a2b238bbdacf534aa30b77454cecde90d47c782a9e2c2722ae297.scope WatchSource:0}: invalid character 'c' looking for beginning of value


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

How reproducible:
v3.10.0-0.67.0

Steps to Reproduce:
1. Setup ocp cluster with crio
2. Check the node log
3.

Actual results:
Tons of "invalid character 'c' looking for beginning of value" errors

Expected results:
Should not have such error

Additional info:
There is no such problem on docker container env.

Comment 1 Antonio Murdaca 2018-06-14 10:46:11 UTC

Fix here https://github.com/kubernetes-incubator/cri-o/pull/1618

Comment 2 Antonio Murdaca 2018-08-27 13:49:22 UTC

Can you re-test with latest openshift and crio?

Comment 3 Antonio Murdaca 2018-08-27 13:50:19 UTC

if it's not working could you please provide a test vm where I can reproduce myself? Thanks

Comment 4 Meng Bo 2018-08-29 07:26:00 UTC

There is no such error on v3.9.41 with cri-o-1.9.14-1.git4e220eb.el7.x86_64

Comment 5 Antonio Murdaca 2018-08-29 09:06:24 UTC

can you move to verified?

Comment 8 errata-xmlrpc 2019-04-09 14:20:17 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:0619