oc delete OpenVSwitch pods stuck in state terminating

Solution Verified - Updated -

Issue

  • After deleting ovs-pods they are stuck on state "terminating". The related SDN ports changes in PodCrashLoop because it cannot connect to an OpenVSwitch.
  • This problem occurs on manual deletion of the pod and while updating cluster via Ansible, where these pods are also deleted to come up with new versions. Then the Ansible playbook stucks at this step.
  • It works using the parameter --force --grace-period=0 but this is not the solution
  • After digging into the process list of the hosts, where this failure occurs there is a process running:

    tail --follow=name /var/log/openvswitch/ovs-vswitchd.log /var/log/openvswitch/ovsdb-server.log
    
  • After killing this process the container is gone and a new one comes up.

  • This is reproducible from the versions 3.11.153 to 3.11.161

Environment

  • Red Hat OpenShift Container Platform(OCP) 3.11

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