Bug 1919966 - release-4.6: Undiagnosed panic detected in pod runtime.go:76: invalid memory address or nil pointer dereference
Summary: release-4.6: Undiagnosed panic detected in pod runtime.go:76: invalid memory ...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: openshift-apiserver
Version: 4.6
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: 4.6.z
Assignee: Lukasz Szaszkiewicz
QA Contact: Xingxing Xia
URL:
Whiteboard:
Depends On: 1919968
Blocks: 1931404
TreeView+ depends on / blocked
 
Reported: 2021-01-25 13:34 UTC by Lukasz Szaszkiewicz
Modified: 2021-02-22 11:15 UTC (History)
9 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Fixes a data race in SerializeObject function in the Kube API server. Previously all sorts of errors including a data race were possible. An attempt to write to a nil writer might have lead to "invalid memory address" or "nil pointer dereference". Sharing the same instance of the writer might have also lead to "index out of range [43] with length 30 and recovered from err index > windowEnd" errors
Clone Of: 1875046
: 1919968 1931404 (view as bug list)
Environment:
Undiagnosed panic detected in pod
Last Closed: 2021-02-17 19:25:10 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github openshift oauth-apiserver pull 38 0 None closed Bug 1919966: fixes a data race in SerializeObject function 2021-02-11 14:46:21 UTC
Github openshift openshift-apiserver pull 182 0 None closed Bug 1919966: fixes a data race in SerializeObject function 2021-02-11 14:46:21 UTC
Red Hat Product Errata RHBA-2021:0424 0 None None None 2021-02-17 19:25:32 UTC

Comment 1 Lukasz Szaszkiewicz 2021-01-25 13:36:46 UTC 
Applies to openshift-apiserver and oauth-apiserver
Comment 4 Xingxing Xia 2021-02-01 10:21:33 UTC 
Discussed in Slack, waiting openshift-apiserver PR to be opened and attached too.
Comment 8 Xingxing Xia 2021-02-07 13:38:56 UTC 
Discussed in Slack with Dev, this was race, not easy to reproduce (and verify), thus still like bug 1919968, use CI search to verify:
Search: openshift-apiserver.*Observed a panic: runtime error: invalid memory address or nil pointer dereference
URL of the search: https://search.ci.openshift.org/?search=openshift-apiserver.*Observed+a+panic%3A+runtime+error%3A+invalid+memory+address+or+nil+pointer+dereference&maxAge=48h&context=1&type=junit&name=release&maxMatches=5&maxBytes=20971520&groupBy=job

Search: oauth-apiserver.*Observed a panic: runtime error: invalid memory address or nil pointer dereference
URL of the search: https://search.ci.openshift.org/?search=oauth-apiserver.*Observed+a+panic%3A+runtime+error%3A+invalid+memory+address+or+nil+pointer+dereference&maxAge=48h&context=1&type=junit&name=release&maxMatches=5&maxBytes=20971520&groupBy=job

Referring to the clarification of the panic, the search results do not see 4.6 OAS and OauthAS panic since the PR merging.
Comment 10 errata-xmlrpc 2021-02-17 19:25:10 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 (OpenShift Container Platform 4.6.17 bug fix 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/RHBA-2021:0424
Note You need to log in before you can comment on or make changes to this bug.