-
Notifications
You must be signed in to change notification settings - Fork 286
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
Upgrade to v0.3.2 all pods crashed #172
Comments
|
The release is reverted, and it's likely that this is around ready handling in #168. Can you please attach the full log? |
Sorry Bro, due to release reverted. I can't get v0.3.2 again. If could, I'll pleasure to provide full logs about dockerd, cri-dockerd and kubelet etc. Thank you. |
You don't have logs from earlier? Or is it possible to build from source? Even a better/more complete description of the reproduction environment (which CNI -- these logs are network related? what workloads?) would help |
Could you please provide me v0.3.2 amd64 binary tarball again? I'll update and reproduce error logs. I didn't build from source. My environment, CNI is Calico v3.25.1. And node description: Name: k8s NetworkUnavailable False Mon, 03 Apr 2023 21:07:04 +0800 Mon, 03 Apr 2023 21:07:04 +0800 CalicoIsUp Calico is running on this node default nfs-client-provisioner-75f8cc789d-629zd 0 (0%) 0 (0%) 0 (0%) 0 (0%) 20d cpu 550m (6%) 100m (1%) |
Closing this issue as it was related to a reverted release. If the issue exists in the current release then we c an take a look |
OS: Debian 11.6
cri-dockered version: 0.3.2
docker-ce version: 23.0.2-1
debian.11bullseyekubernetes version: v1.26.3
After upgraded v0.3.2 all pods failed to start. Rollback to v0.3.1 everything goes well.
The text was updated successfully, but these errors were encountered: