Kubelet segfaults and restarts sporadically

Solution Verified - Updated -

Issue

  • Kubelet in OCP nodes restarts, which leads to the nodes becoming NotReady temporarily. Why does this happen and how can we prevent it?
  • Kubelet panics with an invalid memory address in net.ParseIP
Oct 11 02:44:10 example.com hyperkube[xxxxx]: panic: runtime error: invalid memory address or nil pointer dereference
Oct 11 02:44:10 example.com hyperkube[xxxxx]: [signal SIGSEGV: segmentation violation code=0x1 addr=0x0 pc=0x555a9b]
Oct 11 02:44:10 example.com hyperkube[xxxxx]: goroutine 461 [running]:
Oct 11 02:44:10 example.com hyperkube[xxxxx]: net.ParseIP(0x0, 0xd, 0x441db60, 0x8801, 0xc0071ec2d0)
Oct 11 02:44:10 example.com hyperkube[xxxxx]:         /usr/lib/golang/src/net/ip.go:680 +0x3b
Oct 11 02:44:10 example.com hyperkube[xxxxx]: k8s.io/kubernetes/vendor/k8s.io/utils/net.IsIPv4String(0x0, 0xd, 0x1)
Oct 11 02:44:10 example.com hyperkube[xxxxx]:         /builddir/build/BUILD/openshift-4.8.0/_output/local/go/src/k8s.io/kubernetes/vendor/k8s.io/utils/net/net.go:147 +0x39

Environment

Red Hat OpenShift Container Platform 4.8 (RHOCP4)

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content