-
Notifications
You must be signed in to change notification settings - Fork 717
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
fix rootless e2e tests #2750
Comments
the same is not failing in this "latest" job
very odd...i wonder how the "rootless" mode is related here. |
This comment was marked as abuse.
This comment was marked as abuse.
yeah the contributor confirmed it will be nil |
There are some error messages in etcd log like below. The log is
kubelet exit log
|
that's odd, is it failing to dial the cri socket for some reason? might be worth reporting to sig node if we understand better what's happening.. |
I found the problem. I will send a PR. |
During the upgrade of kubeadm, the kubelet config is corrupt by kubernetes/kubernetes#112000. kubernetes/kubernetes#112062 will fix it. |
makes sense yet the main upgrade job works as mentioned here |
looks like that was the problem |
slack thread in #release-ci-signal
https://kubernetes.slack.com/archives/CN0K3TE2C/p1661502210909039
started failing yesterday
it seems it cannot call
etcd --version
on theetcd-kinder-rootless-control-plane-1
pod in thecluster-info
task, for some reason.the apiserver and etcd pods seem to be running.
https://testgrid.k8s.io/sig-cluster-lifecycle-kubeadm#kubeadm-kinder-rootless-latest
https://prow.k8s.io/view/gs/kubernetes-jenkins/logs/ci-kubernetes-e2e-kubeadm-kinder-rootless-latest/1562823830211137536
i don't see any potential issues in the
before..after
failing commits in k/kkubernetes/kubernetes@b87a436...7627791
The text was updated successfully, but these errors were encountered: