-
Bug
-
Resolution: Unresolved
-
Major
-
None
-
4.17
This is a clone of issue OCPBUGS-42083. The following is the description of the original issue:
—
This test failed 3 times in the last week with the following error:
{{
Unknown macro: { KubeAPIErrorBudgetBurn was at or above info for at least 2m28s on platformidentification.JobType{Release}(maxAllowed=0s): pending for 1h33m52s, firing for 2m28s: Sep 16 21:20:56.839 - 148s E namespace/openshift-kube-apiserver alert/KubeAPIErrorBudgetBurn alertstate/firing severity/critical ALERTS{alertname="KubeAPIErrorBudgetBurn", alertstate="firing", long="6h", namespace="openshift-kube-apiserver", prometheus="openshift-monitoring/k8s", severity="critical", short="30m"}}}}
It didn't fail a single time in the previous month on 4.17 nor in the month before we shipped 4.16 so I'm proposing this as a blocker to be investigated. Below you have the boilerplate Component Readiness text:
Component Readiness has found a potential regression in the following test:
[bz-kube-apiserver][invariant] alert/KubeAPIErrorBudgetBurn should not be at or above info
Probability of significant regression: 99.04%
Sample (being evaluated) Release: 4.17
Start Time: 2024-09-10T00:00:00Z
End Time: 2024-09-17T23:59:59Z
Success Rate: 85.71%
Successes: 18
Failures: 3
Flakes: 0
Base (historical) Release: 4.16
Start Time: 2024-05-28T00:00:00Z
End Time: 2024-06-27T23:59:59Z
Success Rate: 100.00%
Successes: 74
Failures: 0
Flakes: 0
- clones
-
OCPBUGS-42083 alert/KubeAPIErrorBudgetBurn should not be at or above info
- POST
- is blocked by
-
OCPBUGS-42083 alert/KubeAPIErrorBudgetBurn should not be at or above info
- POST
- links to