Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1939943

Summary: `cluster-kube-apiserver-operator check-endpoints` observed a panic: runtime error: invalid memory address or nil pointer dereference
Product: OpenShift Container Platform Reporter: Xingxing Xia <xxia>
Component: kube-apiserverAssignee: Stefan Schimanski <sttts>
Status: CLOSED ERRATA QA Contact: Xingxing Xia <xxia>
Severity: high Docs Contact:
Priority: unspecified    
Version: 4.8CC: aos-bugs, kewang, mfojtik, xxia
Target Milestone: ---   
Target Release: 4.8.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-07-27 22:53:56 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 Xingxing Xia 2021-03-17 10:40:54 UTC
Description of problem:
While verifying in bug 1933599#c2 , saw openshift-apiserver-check-endpoints still uses 0.20.1, which caused the panic in the searched latest 4.8 CI logs. See the bug 1933599#c2 for details. Let me paste the CI job: https://prow.ci.openshift.org/view/gs/origin-ci-test/logs/periodic-ci-openshift-release-master-ci-4.8-e2e-aws-serial/1370497671634096128 . Confirmed with the Dev of bug 1933599, a separate KAS bug is needed, so I file.

Comment 1 Stefan Schimanski 2021-04-14 12:31:56 UTC
We have bumped the operator meanwhile. This should be fixed.

Comment 3 Xingxing Xia 2021-04-21 07:48:49 UTC
Using the steps of bug 1933599#c2 , above issue is not seen any since ON_QA, so moving to VERIFIED.

Comment 6 errata-xmlrpc 2021-07-27 22:53:56 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.8.2 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:2438