SetupNetworkError "Failed to setup network for pod" after OCP 3.4 Upgrade due to SELinux

Issue

After following upgrade process for a 3.3.1 installation to 3.4, the router, docker-registry and registry-console pods are unable to setup their networks when scheduled.

  9m    1s  82  {kubelet ocp-master1.example.com}       Warning FailedSync  Error syncing pod, skipping: failed to "SetupNetwork" for "router-9-deploy_default" with SetupNetworkError: "Failed to setup network for pod \"router-9-deploy_default(b13f4b14-de7e-11e6-968a-52540089f0cc)\" using network plugins \"cni\": failed to Statfs \"/proc/0/ns/net\": no such file or directory; Skipping pod"

  13m   13m 1   {kubelet ocp-master1.example.com}       Warning FailedSync  Error syncing pod, skipping: failed to "SetupNetwork" for "docker-registry-11-3ykik_default" with SetupNetworkError: "Failed to setup network for pod \"docker-registry-11-3ykik_default(01aee4e0-de7c-11e6-a85a-52540089f0cc)\" using network plugins \"cni\": failed to Statfs \"/proc/25346/ns/net\": no such file or directory; Skipping pod"


  16m   23s 46  {kubelet ocp-node2.example.com}     Warning FailedSync  Error syncing pod, skipping: failed to "SetupNetwork" for "registry-console-1-kn442_default" with SetupNetworkError: "Failed to setup network for pod \"registry-console-1-kn442_default(01af2237-de7c-11e6-a85a-52540089f0cc)\" using network plugins \"cni\": failed to Statfs \"/proc/0/ns/net\": no such file or directory; Skipping pod"