Bug 1754606 - 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
high
high
Target Milestone: ---
: 4.2.z
Assignee: Jacob Tanenbaum
QA Contact: zhaozhanqi
URL:
Whiteboard:
: 1758116 1762933 (view as bug list)
Depends On: 1754592
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-09-23 17:08 UTC by chris alfonso
Modified: 2019-10-30 04:45 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1754592
Environment:
Last Closed: 2019-10-30 04:44: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 323 0 None closed Bug 1754606: [release-4.2] Correct the way nodes are computed for alert ClusterIPTablesStale 2020-01-31 19:16:46 UTC
Red Hat Product Errata RHBA-2019:3151 0 None None None 2019-10-30 04:45:04 UTC

Comment 1 Casey Callendrello 2019-10-03 10:36:52 UTC 
*** Bug 1758116 has been marked as a duplicate of this bug. ***
Comment 2 Clayton Coleman 2019-10-17 20:10:17 UTC 
*** Bug 1762933 has been marked as a duplicate of this bug. ***
Comment 3 Clayton Coleman 2019-10-17 20:10:41 UTC 
Impacts 15% of the fleet, fix this in 4.2.1 please.
Comment 5 Weibin Liang 2019-10-24 14:43:46 UTC 
No Cluster level alert for iptables syncs found in https://prow.svc.ci.openshift.org/?job=release-*-4.2*
Comment 7 errata-xmlrpc 2019-10-30 04:44: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-2019:3151
Note You need to log in before you can comment on or make changes to this bug.