OCNE: Kubernetes Pods Using Pod Network Failing To Start With CrashLoopBackOff And Segfault Errors (Exit Code 139) (Doc ID 3000513.1)

Last updated on JANUARY 31, 2024

Applies to:

Symptoms

In OCNE environment, issue of kubernetes pods using pod network failing to start with CrashLoopBackOff error is noticed. The issue happens only on the pods using the pod network and not on the pods using the Host network. For e.g. pods like coredns, istio pods and any app pods using the pod network will notice the failure. But pods like flannel pods which use the host network work without any issues.

When checking the pod logs using kubectl describe command we notice that the pods are failing with Error code 149 segmention fault error. Below is the snippet of error message we notice when running kubectl describe command on the pod.

Changes

None.

Cause

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.