-
Bug
-
Resolution: Duplicate
-
Major
-
None
-
4.17
-
Yes
-
False
-
Component Readiness has found a potential regression in the following test:
[bz-Management Console] clusteroperator/console should not change condition/Available
Probability of significant regression: 99.23%
Sample (being evaluated) Release: 4.17
Start Time: 2024-08-06T00:00:00Z
End Time: 2024-08-12T23:59:59Z
Success Rate: 83.33%
Successes: 15
Failures: 3
Flakes: 0
Base (historical) Release: 4.16
Start Time: 2024-05-31T00:00:00Z
End Time: 2024-06-27T23:59:59Z
Success Rate: 100.00%
Successes: 68
Failures: 0
Flakes: 1
Here is an example job:
The operator seems to be complaining about console route availability issue:
Aug 12 08:29:41.929 E clusteroperator/console condition/Available reason/RouteHealth_FailedGet status/False RouteHealthAvailable: failed to GET route (https://console-openshift-console.apps.ci-op-s8rfswg6-99d3e.vmc-ci.devcluster.openshift.com): Get "https://console-openshift-console.apps.ci-op-s8rfswg6-99d3e.vmc-ci.devcluster.openshift.com": context deadline exceeded (Client.Timeout exceeded while awaiting headers)
But disruption test does not show any console route related disruptions:
- duplicates
-
OCPBUGS-39580 clusteroperator/console: unexpected state transitions during e2e test run
- ASSIGNED