SDN healthcheck unable to reconnect to OVS server.

Solution Verified - Updated -

Issue

  • Restarts of the networking processes (SDN, Proxy, DNS) result in multi-tenant SDN connectivity being lost when the new process comes up. The pods remain reachable while the old process is terminating, but creation results in the existing pods having no connectivity.
  • Systemd unit files are configured so that if systemd restarts OVS (due to crash or upgrade process), then it will restart Openshift components too, so recover is possible as automatically. But if the deletion of the SDN is done manually, for example, as per following command ip link del br0, or as per any miss-configuration error, SDN will stay in an undesirable state until you restart Openshift node and its networking processes.

Environment

  • Openshift Container Platform 3.11 (OCP).

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