Bug 1754592

Summary: cluster level alert fires spuriously
Product: OpenShift Container Platform Reporter: Jacob Tanenbaum <jtanenba>
Component: NetworkingAssignee: Casey Callendrello <cdc>
Networking sub component: openshift-sdn QA Contact: zhaozhanqi <zzhao>
Status: CLOSED ERRATA Docs Contact:
Severity: medium    
Priority: low CC: bbennett, calfonso, ccoleman, nagrawal, weliang
Version: 4.2.0   
Target Milestone: ---   
Target Release: 4.3.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
: 1754606 1758116 1762933 (view as bug list) Environment:
Last Closed: 2020-01-23 11:06:54 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1754606, 1758116, 1762933    

Description Jacob Tanenbaum 2019-09-23 16:21:39 UTC
Cluster level alert for iptables syncs fires spuriously.

Comment 4 Weibin Liang 2019-10-11 14:13:00 UTC
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.

Comment 5 Clayton Coleman 2019-10-17 20:06:27 UTC
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

Comment 6 Clayton Coleman 2019-10-17 20:08:46 UTC
Realized this was target 4.3.0, since it's impacting so much of the fleet with an alert cloning back to 4.2.z and setting to high.

Comment 8 errata-xmlrpc 2020-01-23 11:06:54 UTC
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:0062