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
I don't see it here: https://storage.googleapis.com/origin-ci-test/pr-logs/pull/openshift_cluster-openshift-apiserver-operator/167/pull-ci-openshift-cluster-openshift-apiserver-operator-master-e2e-aws/785/artifacts/e2e-aws/pods/openshift-apiserver-operator_openshift-apiserver-operator-cc99f5d4f-m69qc_operator.log.gz
Verified on 4.0.0-0.ci-2019-03-05-024322. Only 3 instances of this error in the logs.
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
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days