-
Notifications
You must be signed in to change notification settings - Fork 2.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
many pods NotReady after reboot, on crictl inspect i get "state": "SANDBOX_NOTREADY", "netNamespaceClosed": "true" #11139
Comments
Pod sandboxes (control groups) do not survive a reboot. It is expected that pods would need to be recreated after a restart of the node that they are running on. Also, why are you running 1.30.0 instead of a more recent patch release? |
thanks for the answer! |
Generally we recommend using the most recent patch release, yes. They're not ready because you rebooted and the processes were terminated during shutdown.Whenever you reboot a node, all the pods on that node will need to be restarted afterwards. This is normal. |
Environmental Info:
K3s Version:
k3s version v1.30.0+k3s1 (1454953)
go version go1.22.2
Node(s) CPU architecture, OS, and Version:
Linux tegra-ubuntu 5.10.120-tegra #11 SMP PREEMPT Wed Nov 1 13:11:49 CST 2023 aarch64 aarch64 aarch64 GNU/Linux
Cluster Configuration:
single node server + agent
Describe the bug:
after i reboot and i do crictl pods i get many pods not ready. however all kubectl pods are ok.
no empty files exist
find /var/lib/cni/ -size 0
/var/lib/cni/networks/cbr0/lock
these are the errors from journalctl -u k3s:
https://gist.github.com/UriZafrir/70d1c1e4c968cd17329ce143241bd6d0
kubectl get nodes
NAME STATUS ROLES AGE VERSION
tegra-ubuntu Ready control-plane,master 5h22m v1.30.0+k3s1
crictl inspectp gives:
"state": "SANDBOX_NOTREADY":
"netNamespaceClosed": true,
this is true for all NotReady pods.
Steps To Reproduce:
k3s offline install:
#copy images to folder
mkdir -p /var/lib/rancher/k3s/agent/images/
#copy k3s binary to folder
cp k3s-airgap-images-arm64.tar.zst /var/lib/rancher/k3s/agent/images/
chmod +x k3s
cp k3s /usr/local/bin
chmod +x install.sh
INSTALL_K3S_SKIP_DOWNLOAD=true ./install.sh
#copy private registry file to a place k3s expects
cp registries.yaml /etc/rancher/k3s/
sudo systemctl restart k3s
Expected behavior:
should not happen
Actual behavior:
many pods notready
The text was updated successfully, but these errors were encountered: