Bug 1919966
| Summary: | release-4.6: Undiagnosed panic detected in pod runtime.go:76: invalid memory address or nil pointer dereference | |||
|---|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Lukasz Szaszkiewicz <lszaszki> | |
| Component: | openshift-apiserver | Assignee: | Lukasz Szaszkiewicz <lszaszki> | |
| Status: | CLOSED ERRATA | QA Contact: | Xingxing Xia <xxia> | |
| Severity: | high | Docs Contact: | ||
| Priority: | high | |||
| Version: | 4.6 | CC: | alchan, aos-bugs, hgomes, jkaur, kewang, lszaszki, mfojtik, wking, xxia | |
| Target Milestone: | --- | |||
| Target Release: | 4.6.z | |||
| Hardware: | Unspecified | |||
| OS: | Unspecified | |||
| Whiteboard: | ||||
| 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
|
Story Points: | --- | |
| Clone Of: | 1875046 | |||
| : | 1919968 1931404 (view as bug list) | Environment: |
Undiagnosed panic detected in pod
|
|
| Last Closed: | 2021-02-17 19:25:10 UTC | Type: | --- | |
| Regression: | --- | Mount Type: | --- | |
| Documentation: | --- | CRM: | ||
| Verified Versions: | Category: | --- | ||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | ||
| Cloudforms Team: | --- | Target Upstream Version: | ||
| Embargoed: | ||||
| Bug Depends On: | 1919968 | |||
| Bug Blocks: | 1931404 | |||
|
Comment 1
Lukasz Szaszkiewicz
2021-01-25 13:36:46 UTC
Discussed in Slack, waiting openshift-apiserver PR to be opened and attached too. 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. 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 |