Bug 1754592 - cluster level alert fires spuriously
Summary: cluster level alert fires spuriously
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Networking
Version: 4.2.0
Hardware: Unspecified
OS: Unspecified
low
medium
Target Milestone: ---
: 4.3.0
Assignee: Casey Callendrello
QA Contact: zhaozhanqi
URL:
Whiteboard:
Depends On:
Blocks: 1754606 1758116 1762933
TreeView+ depends on / blocked
 
Reported: 2019-09-23 16:21 UTC by Jacob Tanenbaum
Modified: 2020-01-23 11:07 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 1754606 1758116 1762933 (view as bug list)
Environment:
Last Closed: 2020-01-23 11:06:54 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github openshift cluster-network-operator pull 322 0 None closed Bug 1754592: Correct the way nodes are computed for alert ClusterIPTablesStale 2020-08-18 19:55:14 UTC
Red Hat Product Errata RHBA-2020:0062 0 None None None 2020-01-23 11:07:14 UTC

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
Note You need to log in before you can comment on or make changes to this bug.