Bug 2010352
Summary: | OpenShift Alerting Rules Style-Guide Compliance | ||
---|---|---|---|
Product: | OpenShift Container Platform | Reporter: | Brad Ison <brad.ison> |
Component: | kube-controller-manager | Assignee: | Filip Krepinsky <fkrepins> |
Status: | CLOSED ERRATA | QA Contact: | zhou ying <yinzhou> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 4.10 | CC: | aos-bugs, mfojtik |
Target Milestone: | --- | ||
Target Release: | 4.10.0 | ||
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-03-10 16:16:32 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: |
Description
Brad Ison
2021-10-04 13:52:02 UTC
PR is up. Thanks for the explanations. *** Bug 1992537 has been marked as a duplicate of this bug. *** Confirmed with latest ocp , the issue has fixed: [root@localhost ~]# oc get clusterversion NAME VERSION AVAILABLE PROGRESSING SINCE STATUS version 4.10.0-0.nightly-2021-11-22-195410 True False 130m Cluster version is 4.10.0-0.nightly-2021-11-22-195410 name: PodDisruptionBudgetAtLimit expr: max by(namespace, poddisruptionbudget) (kube_poddisruptionbudget_status_current_healthy == kube_poddisruptionbudget_status_desired_healthy) for: 1h labels: severity: warning annotations: description: The pod disruption budget is at minimum disruptions allowed level. The number of current healthy pods is equal to desired healthy pods. summary: The pod disruption budget is preventing further disruption to pods. 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.10.3 security 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. https://access.redhat.com/errata/RHSA-2022:0056 |