Bug 1951167

Summary: undiagnosed panic in hyperkube
Product: OpenShift Container Platform Reporter: Ben Parees <bparees>
Component: NodeAssignee: Harshal Patil <harpatil>
Node sub component: Kubelet QA Contact: Sunil Choudhary <schoudha>
Status: CLOSED DUPLICATE Docs Contact:
Severity: high    
Priority: unspecified CC: aos-bugs, harpatil
Version: 4.8   
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:
Undiagnosed panic detected in journal
Last Closed: 2021-04-21 06:22:55 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 Ben Parees 2021-04-19 17:37:35 UTC 
Description of problem:
nodes/ip-10-0-151-123.us-west-1.compute.internal/journal.gz:Apr 19 14:47:36.973476 ip-10-0-151-123 hyperkube[1418]: E0419 14:47:36.973403    1418 runtime.go:78] Observed a panic: "invalid memory address or nil pointer dereference" (runtime error: invalid memory address or nil pointer dereference)

occurring frequently, see:
https://search.ci.openshift.org/?search=undiagnosed+panic&maxAge=48h&context=1&type=junit&name=&excludeName=&maxMatches=5&maxBytes=20971520&groupBy=job

sample job:
https://prow.ci.openshift.org/view/gs/origin-ci-test/logs/periodic-ci-openshift-release-master-nightly-4.8-e2e-aws-canary/1384139611290210304


Version-Release number of selected component (if applicable):
4.8

Actual results:
hyperkube process appears to be panicking

Expected results:
OCP processes should not panic
Comment 2 Harshal Patil 2021-04-21 06:22:55 UTC 

*** This bug has been marked as a duplicate of bug 1951042 ***