Node NotReady: ovs, sdn or sync pod not getting started or deployed

Issue

• One of the OpenShift nodes remains in state NotReady. In the sdn container we can see the following error.

  I0710 10:53:40.253326   37340 healthcheck.go:29] waiting for OVS to start: dial unix /var/run/openvswitch/db.sock: connect: no such file or directory
  F0710 10:53:40.253342   37340 network.go:46] SDN node startup failed: node SDN setup failed: timed out waiting for the condition
  

• ovs DaemonSet does not schedule pod on a set of OpenShift nodes, causing the Node service failing to start.