-
Bug
-
Resolution: Unresolved
-
Critical
-
None
-
4.19.0
-
Critical
-
None
-
Proposed
-
False
-
(Feel free to update this bug's summary to be more specific.)
Component Readiness has found a potential regression in the following test:
operator conditions kube-apiserver
Significant regression detected.
Fishers Exact probability of a regression: 100.00%.
Test pass rate dropped from 99.46% to 90.48%.
Sample (being evaluated) Release: 4.19
Start Time: 2025-02-27T00:00:00Z
End Time: 2025-03-06T12:00:00Z
Success Rate: 90.48%
Successes: 57
Failures: 6
Flakes: 0
Base (historical) Release: 4.18
Start Time: 2025-02-04T00:00:00Z
End Time: 2025-03-06T12:00:00Z
Success Rate: 99.46%
Successes: 183
Failures: 1
Flakes: 0
View the test details report for additional context.
A selection of baremetal jobs now fail due to the following error:
time="2025-03-06T06:08:48Z" level=info msg="Extracted /usr/bin/k8s-tests-ext.gz for tag hyperkube from quay.io/openshift-release-dev/ocp-v4.0-art-dev@sha256:c21b9b37064cdf3297b44e747ea86ca92269e1e133f5042f8bd3ef9aaeda9e6e (disk size 119671560, extraction duration 7.038773908s)" time="2025-03-06T06:08:48Z" level=info msg="Listing images for \"k8s-tests-ext\"" error: encountered errors while listing tests: failed running '/alabama/.cache/openshift-tests/registry_ci_openshift_org_ocp_release_4_19_0-0_nightly-2025-03-06-043021_f1a1994f6536/k8s-tests-ext list': exit status 1 Output: E0306 06:08:48.426861 116 test_context.go:584] Unknown provider "baremetal". The following providers are known: aws azure gce kubemark local openstack skeleton vsphere {"component":"entrypoint","error":"wrapped process failed: exit status 1","file":"sigs.k8s.io/prow/pkg/entrypoint/run.go:84","func":"sigs.k8s.io/prow/pkg/entrypoint.Options.internalRun","level":"error","msg":"Error executing test process","severity":"error","time":"2025-03-06T06:08:48Z"} error: failed to execute wrapped command: exit status 1 INFO[2025-03-06T06:08:50Z] Step e2e-metal-ipi-serial-ovn-ipv6-baremetalds-e2e-test failed after 22s.
This surfaces in the operator conditions tests for kube and openshift APIs as we fail fast, before these can stabilize, and thus the cluster does not appear ready when we expect it to be.
It is believed to have been caused by https://github.com/openshift/kubernetes/pull/2229
