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
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
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.
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