Bug 1951167 - undiagnosed panic in hyperkube
Summary: undiagnosed panic in hyperkube
Keywords:
Status: CLOSED DUPLICATE of bug 1951042
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Node
Version: 4.8
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
: 4.8.0
Assignee: Harshal Patil
QA Contact: Sunil Choudhary
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-04-19 17:37 UTC by Ben Parees
Modified: 2021-04-21 06:22 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Undiagnosed panic detected in journal
Last Closed: 2021-04-21 06:22:55 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

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


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