Cloned back to 4.2 because 15% of clusters are reporting it. +++ This bug was initially created as a clone of Bug #1754592 +++ Cluster level alert for iptables syncs fires spuriously. --- Additional comment from on 2019-09-23 12:30:46 EDT --- PR posted: https://github.com/openshift/cluster-network-operator/pull/322 --- Additional comment from errata-xmlrpc on 2019-10-04 06:42:38 EDT --- Bug report changed to ON_QA status by Errata System. A QE request has been submitted for advisory RHBA-2019:46256-02 https://errata.devel.redhat.com/advisory/46256 --- Additional comment from Luke Meyer on 2019-10-04 06:42:50 EDT --- Elliott changed bug status from ('MODIFIED',) to ON_QA. --- Additional comment from Weibin Liang on 2019-10-11 10:13:00 EDT --- https://github.com/openshift/cluster-network-operator/pull/322 merged 9 days ago and latest e2e AWS testing passed on this fixing. QE verify this bug based on above information. --- Additional comment from Clayton Coleman on 2019-10-17 16:06:27 EDT --- This didn't get back ported into 4.2, it looks like it merged to master after the release-4.2 split. 15% of clusters in the wild are firing this alert. Needs to be fixed in 4.2.1
*** This bug has been marked as a duplicate of bug 1754606 ***