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
[microk8s 1.21 - Raspberry Pi 4] snap.microk8s.daemon-kubelite service continually restarts non-stop #2211
Comments
@kevin-leong thank you for reporting. This was also reported here #2204. |
Thanks, I took a look at #2204. I will similar test the fix once it gets to edge. The other thing that comes to mind is that Raspberry Pi do not have a (hardware) RTC, so on boot up the Raspberry Pi may have a really out-of-sync time (in the past) and so ntp/chrony/systemd-timesyncd needs to sync the time on the host. So if the time was not sync yet before snap.microk8s.* services starts, then relying on (calculating) time could possibly cause issues... Just to note... On my Raspberry Pi:
On my VM (that on my desktop):
|
@kevin-leong just to confirm your notes I also ran My results match yours
|
Could you try the 1.21/edge channel?
or in an existing deployment
|
I updated to the below on one of my nodes, and it looks like it fixed after testing a reboot. latest/edge: v1.21.0 2021-04-28 (2176) 168MB classic When will this fix hit the latest/stable branch? This is a critical bug I think. |
@kevin-leong, we are working on releasing this fix to stable right now. |
@ktsakalozos - thanks it looks like it hit latest/stable. I refresh to this version, and rebooted my nodes and they came up fine now. Thanks, closing this. |
I am using microk8s 1.21 (with Ubuntu 21.04) on my Raspberry Pi 4 cluster never seems to want to come up....
Looking at "journalctl -u snap.microk8s.daemon-kubelite.service", I am notice that this service is just continuing to restart non-stop for "Waiting for containerd socket /var/snap/microk8s/common/run/containerd.sock to appear".
Looking "journalctl -u snap.microk8s.daemon-containerd.service", it looks like it is trying to "cleaning up dead shim".
I am not sure what is going wrong here. I didn't have this issue with 1.20.6. Looking at the git commit log for master, I notice this commit: 25fb636. Does this commit have something to do with this?
I appreciate if someone can please take a look at this issue, as this pretty much makes my cluster unusable and pretty much broken.....
Thank you.
Version:
$ snap info microk8s | egrep -i "latest/stable|installed"
tracking: latest/stable
latest/stable: v1.21.0 2021-04-21 (2129) 165MB classic
installed: v1.21.0 (2129) 165MB classic
snap.microk8s.daemon-kubelite.service show the below:
snap.microk8s.daemon-containerd.service show the below:
The text was updated successfully, but these errors were encountered: