Bug 1885463 - NoRunningOvnMaster alert falsely triggered
Summary: NoRunningOvnMaster alert falsely triggered
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Networking
Version: 4.6
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: 4.6.0
Assignee: Juan Luis de Sousa-Valadas
QA Contact: Anurag saxena
URL:
Whiteboard:
Depends On: 1885165
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-10-06 03:18 UTC by OpenShift BugZilla Robot
Modified: 2020-10-27 16:48 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-10-27 16:47:49 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github openshift cluster-network-operator pull 826 0 None closed [release-4.6] Bug 1885463: Fix ovnkube metrics 2020-12-01 19:32:32 UTC
Red Hat Product Errata RHBA-2020:4196 0 None None None 2020-10-27 16:48:13 UTC

Description OpenShift BugZilla Robot 2020-10-06 03:18:30 UTC
+++ This bug was initially created as a clone of Bug #1885165 +++

Description of problem:
NoRunningOvnMaster is triggered even though


Version-Release number of selected component (if applicable):
Current 4.6 master branch

How reproducible:
Always


Steps to Reproduce:
1. Launch a cluster
2. Wait 15 minutes after the cluster installation

Actual results:
Alert is triggered even if ovnkubernetes is reporting metrics

Expected results:
Alert isn't triggered unless ovnkubernetes isn't reporting metrics

Additional info:

Comment 3 Anurag saxena 2020-10-09 08:03:28 UTC
No alerts are observed on 4.6.0-0.nightly-2020-10-09-014415. /LGTM

Comment 5 errata-xmlrpc 2020-10-27 16:47:49 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 (OpenShift Container Platform 4.6 GA Images), 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:4196


Note You need to log in before you can comment on or make changes to this bug.