-
Bug
-
Resolution: Done-Errata
-
Normal
-
4.15
-
No
-
False
-
-
* Previously, the {product-title} web console terminated unexpectedly if authentication discovery failed on the first attempt. With this update, authentication initialization was updated to retry up to 5 minutes before failing.
-
Bug Fix
-
In Progress
This is a clone of issue OCPBUGS-29479. The following is the description of the original issue:
—
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: 100.00%
Sample (being evaluated) Release: 4.15
Start Time: 2024-02-08T00:00:00Z
End Time: 2024-02-14T23:59:59Z
Success Rate: 91.30%
Successes: 63
Failures: 6
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: 735
Failures: 0
Flakes: 0
Note: When you look at the link above you will notice some of the failures mention the bare metal operator. That's being investigated as part of https://issues.redhat.com/browse/OCPBUGS-27760. There have been 3 cases in the last week where the console was in a fail loop. Here's an example:
We need help understanding why this is happening and what needs to be done to avoid it.
- clones
-
OCPBUGS-29479 excessive Back-off restarting failed container console
- Closed
- is blocked by
-
OCPBUGS-29479 excessive Back-off restarting failed container console
- Closed
- links to
-
RHBA-2024:3889 OpenShift Container Platform 4.15.z bug fix update