The test lists all interfaces on the host without any ordering, and thus captures pod interfaces that are long gone by the time it tries to use the interface name for the test.
Example: https://prow.ci.openshift.org/view/gs/origin-ci-test/pr-logs/pull/openshift_cluster-network-operator/1472/pull-ci-openshift-cluster-network-operator-master-e2e-network-migration/1532342201864949760
https://prow.ci.openshift.org/view/gs/origin-ci-test/pr-logs/pull/openshift_cluster-network-operator/1472/pull-ci-openshift-cluster-network-operator-master-e2e-ovn-hybrid-step-registry/1532342204066959360
The current fix broke the nightly runs with this test failure: "pod sysctls should not affect node" Example run: https://prow.ci.openshift.org/view/gs/origin-ci-test/logs/aggregated-azure-ovn-upgrade-4.11-micro-release-openshift-release-analysis-aggregator/1533147727993507840
Dan can this be moved to verified?
Yes, this has not been seen in jobs for quite a while.
OCP is no longer using Bugzilla and this bug appears to have been left in an orphaned state. If the bug is still relevant, please open a new issue in the OCPBUGS Jira project: https://issues.redhat.com/projects/OCPBUGS/summary