This bug was initially created as a copy of Bug #1841828 I am copying this bug because: Description of problem: Sometimes the ovnkube-master stops processing pod updates https://storage.googleapis.com/origin-ci-test/pr-logs/pull/openshift_ovn-kubernetes/174/pull-ci-openshift-ovn-kubernetes-master-e2e-gcp-ovn/1176/artifacts/e2e-gcp-ovn/pods/openshift-ovn-kubernetes_ovnkube-master-82blj_ovnkube-master.log at 15:14 Version-Release number of selected component (if applicable): 4.5 How reproducible: Seems to happen in about 1-in-20 CI runs.
*** Bug 1843396 has been marked as a duplicate of this bug. ***
Based on [1], this series should address CI flakes for: [sig-network] NetworkPolicy [LinuxOnly] NetworkPolicy between server and client should enforce policy based on PodSelector with MatchExpressions[Feature:NetworkPolicy] Copying the test name in here so it turns up in Sippy results as a non-dup bug. [1]: https://bugzilla.redhat.com/show_bug.cgi?id=1845740#c2
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2020:2409
Removing UpgradeBlocker from this older bug, to remove it from the suspect queue described in [1]. If you feel like this bug still needs to be a suspect, please add keyword again. [1]: https://github.com/openshift/enhancements/pull/475