-
Notifications
You must be signed in to change notification settings - Fork 706
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
kubeadm: fix broken e2e tests for 1.21 #2380
Comments
looks like the problem is the new bucket we switched to here. https://console.cloud.google.com/storage/browser/_details/k8s-release-dev/ci/latest-1.20.txt resolves to the latest version reported by https://dl.k8s.io/ci/latest-1.20.txt is the valid one: |
lets keep this open until the tests become green: checking https://console.cloud.google.com/storage/browser/_details/k8s-release-dev/ci/latest-1.20.txt still points to an old tag. |
It seems that the job did not execute successfully. |
looking at the logs i don't understand why it's failing. i see this:
|
I opened a fix for this yesterday but test-infra is having merging issues (ref: kubernetes/test-infra#20586 (comment)) |
thanks @spiffxp |
kubernetes/test-infra#20586 + kubernetes/test-infra#20624 indeed fixed the 2 failing tests 🎉 /close |
@neolit123: 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. |
we have a couple of failing jobs, which i think happened after the version bumps for 1.21:
kubernetes/kubernetes@7791bbe
https://testgrid.k8s.io/sig-cluster-lifecycle-kubeadm#kubeadm-kinder-latest-on-1-20
this i failing in kubeadm init under kinder when the
kubeadm config images list
is called. i tried the isolated command and it works, so it seems to be failing only under kinder for some reason.https://testgrid.k8s.io/sig-cluster-lifecycle-kubeadm#kubeadm-kinder-upgrade-1-20-latest
upgrade is failing with:
then reset timeouts (runs more than 5 min)
The text was updated successfully, but these errors were encountered: