OCP4: Pod ovnkube-node stuck in CrashLoopBackOff when MultiNetworkPolicy has port defined as nil

Solution Verified - Updated -

Issue

  • Pod ovnkube-node pods is stuck in CrashLoopBackOff with pod status of:

    message: back-off 5m0s restarting failed container=ovnkube-controller pod=ovnkube-node-123abc_openshift-ovn-kubernetes
        reason: CrashLoopBackOff

  • After updating MultiNetworkPolicy ovnkube-controller is restarting

  • The ovnkube-controller container shows panic in logs
    panic: runtime error: invalid memory address or nil pointer dereference

Environment

OpenShift Container Platform
- 4.14
- 4.15
- 4.16
- 4.17
- 4.18

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