-
Notifications
You must be signed in to change notification settings - Fork 1.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Tests running on k8s latest commit are failing #10142
Comments
/triage accepted |
Should be fixed by bumping kind via: Root-cause: kind fix: The issue started when kubekins images got bumped to a version which include docker >= v25.0.0 (to be more specific: Only jobs on main are currently affected, because we don't build latest-ci on old branches. If we ever want to do the same on release-1.6 (or older) we need this fix too or a proper workaround (e.g. via |
/assign @cahillsf |
Back to green since merged. /close |
@chrischdi: Closing this issue. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
Which jobs are failing?
Jobs that run on k8s latest commit
Which tests are failing?
When testing K8S conformance with K8S latest ci [Conformance] [K8s-Install-ci-latest] Should create a workload cluster and run kubetest
When upgrading a workload cluster using ClusterClass and testing K8S conformance [Conformance] [K8s-Upgrade] [ClusterClass] Should create and upgrade a workload cluster and eventually run kubetest
Since when has it been failing?
Failed between this time: 16:26 EET 08-02-2024 - 00:29 EET 09-02-2024
After that it went green for a few hours: 02:30 EET 09-02-2024 - 16:31 EET 09-02-2024
And started failing again after: 18:32 EET 09-02-2024
Testgrid link
https://testgrid.k8s.io/sig-cluster-lifecycle-cluster-api#capi-e2e-conformance-ci-latest-main
Reason for failure (if possible)
The machine is stuck in provisioning state and journalctl logs we see this error:
PullImage \"registry.k8s.io/kube-apiserver:v1.30.0-alpha.1.154_73f19e4c0162a2\" failed" error="rpc error: code = NotFound desc = failed to pull and unpack image \"registry.k8s.io/kube-apiserver:v1.30.0-alpha.1.154_73f19e4c0162a2\": failed to resolve reference \"registry.k8s.io/kube-apiserver:v1.30.0-alpha.1.154_73f19e4c0162a2\": registry.k8s.io/kube-apiserver:v1.30.0-alpha.1.154_73f19e4c0162a2: not found"
Since these tests run on k8s latest commit we build kindest/node image locally with the latest commit of k8s and these k8s images should already be in kindest/node. But we are getting this error for some reason.
Anything else we need to know?
kubekins-e2e image has been changed a lot since this test started failing. ref: kubernetes/test-infra#31961
Label(s) to be applied
/kind failing-test
One or more /area label. See https://github.com/kubernetes-sigs/cluster-api/labels?q=area for the list of labels.
The text was updated successfully, but these errors were encountered: