-
Bug
-
Resolution: Not a Bug
-
Critical
-
None
-
4.17, 4.18
Component Readiness has found a potential regression in the following test:
[bz-Routing] clusteroperator/ingress should not change condition/Available
Probability of significant regression: 97.63%
Sample (being evaluated) Release: 4.17
Start Time: 2024-09-01T00:00:00Z
End Time: 2024-09-09T23:59:59Z
Success Rate: 89.29%
Successes: 25
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: 67
Failures: 0
Flakes: 0
It is worth mentioning that in two of the three failures, ingress operator went available=false at the same time image registry went available=false. This is one example.
Team can investigate, and if legit reason exists, please create an exception with origin and address it at proper time: https://github.com/openshift/origin/blob/4557bdcecc10d9fa84188c1e9a36b1d7d162c393/pkg/monitortests/clusterversionoperator/legacycvomonitortests/operators.go#L90
Since this is appearing on component readiness dashboard and the management depends on a green dashboard to make release decisions, please give the initial investigation a high priority. If an exception is needed, please contact TRT team to triage the issue.
- clones
-
OCPBUGS-41527 ingress operator changed condition/Available to false during non-upgrade job
- MODIFIED