Bug 1990610 - Panic in the cluster-kube-apiserver-operator startup monitor enablement check
Summary: Panic in the cluster-kube-apiserver-operator startup monitor enablement check
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: kube-apiserver
Version: 4.9
Hardware: Unspecified
OS: Unspecified
high
medium
Target Milestone: ---
: 4.9.0
Assignee: David Eads
QA Contact: Rahul Gangwar
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-08-05 17:49 UTC by Stephen Benjamin
Modified: 2021-10-18 17:45 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-10-18 17:45:05 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github openshift cluster-kube-apiserver-operator pull 1202 0 None None None 2021-08-05 17:57:16 UTC
Red Hat Product Errata RHSA-2021:3759 0 None None None 2021-10-18 17:45:20 UTC

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


Note You need to log in before you can comment on or make changes to this bug.