Description of problem:
NoRunningOvnMaster is triggered even though
Version-Release number of selected component (if applicable):
Current 4.6 master branch
Steps to Reproduce:
1. Launch a cluster
2. Wait 15 minutes after the cluster installation
Alert is triggered even if ovnkubernetes is reporting metrics
Alert isn't triggered unless ovnkubernetes isn't reporting metrics
Increasing priority to urgent because we want this verified so that we can try to get it merged in 4.6.0 soon.
Steps to verify:
1- launch a 4.6 OVN cluster
2- login into prometheus (prometheus as in "http://prometheus-k8s-openshift-monitoring.<route default subdomain>" , not grafana)
3- Go to status -> targets
4- Look for the two OVN targets (just control+f ovn) and check that both have state UP
Lowered to medium because the 4.6 bug already merged.
No alerts are triggered. Verified.
OVN targets in prometheus also all have status UP.
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 (Moderate: OpenShift Container Platform 4.7.0 security, bug fix, and enhancement update), and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.