-
Bug
-
Resolution: Done-Errata
-
Normal
-
4.15, 4.16
-
Moderate
-
No
-
5
-
Metal Platform 248, Metal Platform 249, Metal Platform 250
-
3
-
False
-
I noticed this today when looking at component readiness. A ~5% decrease in instability may seem minor, but these can certainly add up. This test passed 713 times in a row on 4.14. You can see today's failure here.
Details below:
-------
Component Readiness has found a potential regression in [sig-cluster-lifecycle] pathological event should not see excessive Back-off restarting failed containers.
Probability of significant regression: 99.96%
Sample (being evaluated) Release: 4.15
Start Time: 2024-01-17T00:00:00Z
End Time: 2024-01-23T23:59:59Z
Success Rate: 94.83%
Successes: 55
Failures: 3
Flakes: 0
Base (historical) Release: 4.14
Start Time: 2023-10-04T00:00:00Z
End Time: 2023-10-31T23:59:59Z
Success Rate: 100.00%
Successes: 713
Failures: 0
Flakes: 4
- blocks
-
OCPBUGS-29787 excessive Back-off restarting failed containers
- Closed
- duplicates
-
OCPBUGS-25766 Cluster Baremetal operator should use a leader lock
- Closed
-
OCPBUGS-29153 Cluster Baremetal operator should use a leader lock
- Closed
- is cloned by
-
OCPBUGS-29787 excessive Back-off restarting failed containers
- Closed
- links to
-
RHEA-2024:0041 OpenShift Container Platform 4.16.z bug fix update