Bug 1990610

Summary:	Panic in the cluster-kube-apiserver-operator startup monitor enablement check
Product:	OpenShift Container Platform	Reporter:	Stephen Benjamin <stbenjam>
Component:	kube-apiserver	Assignee:	David Eads <deads>
Status:	CLOSED ERRATA	QA Contact:	Rahul Gangwar <rgangwar>
Severity:	medium	Docs Contact:
Priority:	high
Version:	4.9	CC:	aos-bugs, kewang, mfojtik, xxia
Target Milestone:	---
Target Release:	4.9.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2021-10-18 17:45:05 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:

Description Stephen Benjamin 2021-08-05 17:49:48 UTC

Description of problem:

It's possible to panic in the startup monitor enablement check:

pods/openshift-kube-apiserver-operator_kube-apiserver-operator-5b44fc77bf-vntjr_kube-apiserver-operator.log.gz:E0805 05:07:51.594471       1 runtime.go:78] Observed a panic: "invalid memory address or nil pointer dereference" (runtime error: invalid memory address or nil pointer dereference)
pods/openshift-kube-apiserver-operator_kube-apiserver-operator-5b44fc77bf-vntjr_kube-apiserver-operator.log.gz:E0805 05:07:51.619717       1 runtime.go:78] Observed a panic: "invalid memory address or nil pointer dereference" (runtime error: invalid memory address or nil pointer dereference)


See: 
https://prow.ci.openshift.org/view/gs/origin-ci-test/logs/periodic-ci-openshift-release-master-ci-4.9-e2e-gcp-upgrade/1423126561342623744

Comment 2 Rahul Gangwar 2021-08-19 05:21:03 UTC

There is no panic error found now in upgrade CI jobs.

yes|w3m -dump -cols 200 'https://search.ci.openshift.org/?search=invalid+memory+address+or+nil+pointer+dereference&maxAge=168h&context=1&type=junit&name=4%5C.9&excludeName=&maxMatches=5&maxBytes=20971520&groupBy=job' | grep "periodic-ci-openshift-release-master.*4.9-e2e-.*-upgrade$"|wc -l

   0

Comment 3 Ke Wang 2021-08-19 06:17:07 UTC

If without above limit under grep, there are other panics: https://search.ci.openshift.org/?search=kube-apiserver-operator.*invalid+memory+address+or+nil+pointer+dereference&maxAge=168h&context=1&type=junit&name=4%5C.9&excludeName=&maxMatches=5&maxBytes=20971520&groupBy=job. Need to confirm with Dev.

Comment 6 errata-xmlrpc 2021-10-18 17:45:05 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 (Moderate: OpenShift Container Platform 4.9.0 bug fix and security update), 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/RHSA-2021:3759