Bug 1974183
| Summary: | PodDisruptionBudgetAtLimit alert is fired in OVN SNO cluster | ||||||
|---|---|---|---|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Junqi Zhao <juzhao> | ||||
| Component: | Networking | Assignee: | Ben Pickard <bpickard> | ||||
| Networking sub component: | ovn-kubernetes | QA Contact: | Anurag saxena <anusaxen> | ||||
| Status: | CLOSED DUPLICATE | Docs Contact: | |||||
| Severity: | medium | ||||||
| Priority: | medium | CC: | pstrick, vpickard | ||||
| Version: | 4.8 | Keywords: | Reopened | ||||
| Target Milestone: | --- | ||||||
| Target Release: | --- | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2022-02-15 16:38:15 UTC | Type: | Bug | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Embargoed: | |||||||
| Attachments: |
|
||||||
SNO is GA now in 4.9 [1] and this still occurs when OVN-kubernetes is used. Also, the documentation for SNO uses OVNKubernetes in the example install config [2] which means customers are even more likely to get these alerts. Reopening per request. [1] https://www.redhat.com/en/blog/meet-single-node-openshift-our-smallest-openshift-footprint-edge-architectures [2] Step 6 at https://docs.openshift.com/container-platform/4.9/installing/installing_sno/install-sno-installing-sno.html#generating-the-discovery-iso-manually_install-sno-installing-sno-with-the-assisted-installer (In reply to Patrick Strick from comment #2) > SNO is GA now in 4.9 [1] and this still occurs when OVN-kubernetes is used. > Also, the documentation for SNO uses OVNKubernetes in the example install > config [2] which means customers are even more likely to get these alerts. > Reopening per request. > > [1] > https://www.redhat.com/en/blog/meet-single-node-openshift-our-smallest- > openshift-footprint-edge-architectures > [2] Step 6 at > https://docs.openshift.com/container-platform/4.9/installing/installing_sno/ > install-sno-installing-sno.html#generating-the-discovery-iso- > manually_install-sno-installing-sno-with-the-assisted-installer FYI, same issue happen in 4.10 SNO cluster, see bug 2037721, among the many PDBs, only openshift-ovn-kubernetes fires PodDisruptionBudgetAtLimit alert |
Created attachment 1792596 [details] PodDisruptionBudgetAtLimit alert Description of problem: OVN SNO cluster, PodDisruptionBudgetAtLimit alert is fired for openshift-ovn-kubernetes # oc get node NAME STATUS ROLES AGE VERSION master-00.***.qe.devcluster.openshift.com Ready master,worker 3h11m v1.21.0-rc.0+120883f # oc get network/cluster -oyaml ......... spec: clusterNetwork: - cidr: 10.128.0.0/14 hostPrefix: 23 externalIP: policy: {} networkType: OVNKubernetes ......... alert detail ......... alert: PodDisruptionBudgetAtLimit expr: max by(namespace, poddisruptionbudget) (kube_poddisruptionbudget_status_current_healthy == kube_poddisruptionbudget_status_desired_healthy) for: 1h labels: severity: warning annotations: message: The pod disruption budget is preventing further disruption to pods because it is at the minimum allowed level. ......... search in prometheus max by(namespace, poddisruptionbudget) (kube_poddisruptionbudget_status_current_healthy == kube_poddisruptionbudget_status_desired_healthy) result is {namespace="openshift-ovn-kubernetes", poddisruptionbudget="ovn-raft-quorum-guard"} # oc -n openshift-ovn-kubernetes get PodDisruptionBudget NAME MIN AVAILABLE MAX UNAVAILABLE ALLOWED DISRUPTIONS AGE ovn-raft-quorum-guard 1 N/A 0 172m maybe should not have PodDisruptionBudget for openshift-ovn-kubernetes in SNO cluster Version-Release number of selected component (if applicable): 4.8.0-0.nightly-2021-06-16-020345 How reproducible: always Steps to Reproduce: 1. see the description 2. 3. Actual results: Expected results: Additional info: