Bug 1665599

Summary: openshift-apiserver: many "unable to encode watch object: expected pointer, but got invalid kind" errors
Product: OpenShift Container Platform Reporter: Mike Fiedler <mifiedle>
Component: MasterAssignee: David Eads <deads>
Status: CLOSED ERRATA QA Contact: Xingxing Xia <xxia>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 4.1.0CC: aos-bugs, deads, jokerman, mfojtik, mirollin, mmccomas
Target Milestone: ---Flags: mirollin: needinfo? (deads)
mirollin: needinfo? (deads)
Target Release: 4.1.0   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-06-04 10:41:49 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:
Attachments:
Description Flags
openshift-apiserver pod log none

Description Mike Fiedler 2019-01-11 21:56:17 UTC
Created attachment 1520146 [details]
openshift-apiserver pod log

Description of problem:

The openshift-apiserver pod logs show many error messages:

E0111 21:36:05.155595       1 watch.go:212] unable to encode watch object: expected pointer, but got invalid kind 

They are not at regular intervals


Version-Release number of selected component (if applicable): 4.0.0-0.nightly-2019-01-10-165754


How reproducible: Always


Steps to Reproduce:
1. Install typical 3 master/3 worker next gen cluster on AWS using the OCP payload (4.0.0-0.nightly-2019-01-10-165754)
2. oc logs -n openshift-apiserver <apiserver_pod>

Actual results:
Many instances of

E0111 21:36:05.155595       1 watch.go:212] unable to encode watch object: expected pointer, but got invalid kind 


Additional info:

Full pod log attached

Comment 2 Mike Fiedler 2019-03-07 19:13:55 UTC
Verified on 4.0.0-0.ci-2019-03-05-024322.   Only 3 instances of this error in the logs.

Comment 5 errata-xmlrpc 2019-06-04 10:41:49 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:0758