Description of problem: PodDisruptionBudgetAtLimit Warning alert when CR replica count is zero. Version-Release number of selected component (if applicable): 4.7 How reproducible: Everytime Steps to Reproduce: 1. oc new-project test 2. oc new-app httpd 3. oc create -f pdb $ cat pdb.yaml ~~~ apiVersion: policy/v1beta1 kind: PodDisruptionBudget metadata: name: my-pdb spec: maxUnavailable: 1 selector: matchLabels: deployment: httpd ~~~ $ oc get pdb NAME MIN AVAILABLE MAX UNAVAILABLE ALLOWED DISRUPTIONS AGE my-pdb N/A 0 0 3h27m 4. oc scale deployment httpd --replicas=0 5. Wait for some time alert will be triggered at the console. Actual results: unexpected warning alert Expected results: As we are intentionally dropping down the replicas it should not generate an alert.
I’m adding UpcomingSprint, because I was occupied by fixing bugs with higher priority/severity, developing new features with higher priority, or developing new features to improve stability at a macro level. I will revisit this bug next sprint.
Thanks, yes I think it makes sense to not fire an alert if there is no application to disrupt (the alert triggers even if there is no deployment)
can't see this alter with latest payload : 4.11.0-0.nightly-2022-06-04-014713
We can backport to 4.10. But for 4.9 depends on how critical is this for the customer?
I see. Opened a prerequisite backport https://bugzilla.redhat.com/show_bug.cgi?id=2116983 to start backporting this fix to 4.10 soon
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 (Important: OpenShift Container Platform 4.11.0 bug fix and 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:5069
prerequisites merged, I have opened a backport to 4.10 in jira https://issues.redhat.com/browse/OCPBUGS-466
merged - should be in the next 4.10 release