-
Story
-
Resolution: Done
-
Normal
-
None
-
None
-
None
-
None
-
False
-
-
False
-
None
-
None
-
None
-
Rejected
-
None
Description of problem:
Use NoRunningOvnControlPlane.md and NoOvnClusterManagerLeader.md in https://github.com/openshift/runbooks/tree/master/alerts/cluster-network-operator
Version-Release number of selected component (if applicable):
4.14.0-0.nightly-2023-08-28-154013
How reproducible:
Always
Steps to Reproduce:
[weliang@weliang openshift-tests-private]$ oc get clusterversionNAME VERSION AVAILABLE PROGRESSING SINCE STATUSversion 4.14.0-0.nightly-2023-08-28-154013 True False 58m Cluster version is 4.14.0-0.nightly-2023-08-28-154013[weliang@weliang openshift-tests-private]$ oc -n openshift-ovn-kubernetes get PrometheusRule master-rules -o jsonpath={.spec.groups[*].rules[*].alert}V4SubnetAllocationThresholdExceeded V6SubnetAllocationThresholdExceeded NoRunningOvnControlPlane NoOvnClusterManagerLeader NorthboundStale SouthboundStale OVNKubernetesNorthboundDatabaseCPUUsageHigh OVNKubernetesSouthboundDatabaseCPUUsageHigh
In latest OVN-IC cluster, two alerts of NoRunningOvnMaster and NoOvnMasterLeader were updated to be NoRunningOvnControlPlane and NoOvnClusterManagerLeader
Please update NoRunningOvnMaster.md and NoOvnMasterLeader.md to NoRunningOvnControlPlane.md and NoOvnClusterManagerLeader.md in https://github.com/openshift/runbooks/tree/master/alerts/cluster-network-operator
Actual results:
NoRunningOvnMaster.md and NoOvnMasterLeader.md
Expected results:
NoRunningOvnControlPlane.md and NoOvnClusterManagerLeader.md
Additional info:
