[RHOCP 4] ovn-ipsec-containerized pod in CrashLoopBackOff state leading network operator to degrade

Solution Verified - Updated -

Issue

  • After enabling IPsec encryption in OpenShift Container Platform 4.14.10, network cluster operator degrades and ovn-ipsec-containerized pod remains in CrashLoopBackOff state
  • ovn-ipsec-containerized pod high restart count
  • Network operator degraded with error DaemonSet "/openshift-ovn-kubernetes/ovn-ipsec-containerized" rollout is not making progress - pod ovn-ipsec-containerized-xxxx is in CrashLoopBackOff State

Environment

  • Red Hat OpenShift Container Platform (RHOCP)
    • 4
  • Container Network Interface (CNI)
    • OVNKubernetes

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