# Microk8s in permanent failed state on reboot ( raspberry pi 4, affects single and multi node cluster )

**URL:** <https://discuss.kubernetes.io/t/microk8s-in-permanent-failed-state-on-reboot-raspberry-pi-4-affects-single-and-multi-node-cluster/15661>\
**Category:** microk8s\
**Tags:** microk8s\
**Created:** [April 24, 2021, 5:56pm UTC](https://discuss.kubernetes.io/t/microk8s-in-permanent-failed-state-on-reboot-raspberry-pi-4-affects-single-and-multi-node-cluster/15661 "2021-04-24T17:56:32Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![horvatic](https://sea2.discourse-cdn.com/flex016/user_avatar/discuss.kubernetes.io/horvatic/32/7332_2.png) [@horvatic](https://discuss.kubernetes.io/u/horvatic)\
**Post date:** [April 24, 2021, 5:56pm UTC](https://discuss.kubernetes.io/t/microk8s-in-permanent-failed-state-on-reboot-raspberry-pi-4-affects-single-and-multi-node-cluster/15661/1 "2021-04-24T17:56:32Z")

</div>

Running on a raspberry pi 4, ubuntu 20.04 LTS fresh install. When rebooting there is a possibility of a permanent failed state. When this happens this message will appear: `microk8s is not running. Use microk8s inspect for a deeper inspection.`

Running: `microk8s start` or `microk8s stop; microk8s start` will not solve the issues  
Running: `microk8s reset` will also not solve the issue

rebooting will also not solve the issue

---

<div class="post-metadata">

**Author:** ![horvatic](https://sea2.discourse-cdn.com/flex016/user_avatar/discuss.kubernetes.io/horvatic/32/7332_2.png) [@horvatic](https://discuss.kubernetes.io/u/horvatic)\
**Post date:** [April 24, 2021, 6:30pm UTC](https://discuss.kubernetes.io/t/microk8s-in-permanent-failed-state-on-reboot-raspberry-pi-4-affects-single-and-multi-node-cluster/15661/2 "2021-04-24T18:30:01Z")

</div>

Before a reboot running a `microk8 stop` will stop the issue. BUT the issue will still happen sometimes on an snap auto update of microk8s

---

<div class="post-metadata">

**Author:** ![horvatic](https://sea2.discourse-cdn.com/flex016/user_avatar/discuss.kubernetes.io/horvatic/32/7332_2.png) [@horvatic](https://discuss.kubernetes.io/u/horvatic)\
**Post date:** [April 26, 2021, 3:45pm UTC](https://discuss.kubernetes.io/t/microk8s-in-permanent-failed-state-on-reboot-raspberry-pi-4-affects-single-and-multi-node-cluster/15661/3 "2021-04-26T15:45:37Z")

</div>

Posting this as an issue on the git-repo

EDIT: issue is fixed, as it was a bug. Info here:

> <https://github.com/ubuntu/microk8s/issues/2204>
>
> Running on a raspberry pi 4, ubuntu 20.04 LTS fresh install. When rebooting ther…e is a possibility of a permanent failed state. When this happens this message will appear: microk8s is not running. Use microk8s inspect for a deeper inspection.
> 
> Running: microk8s inspect shows no errors
> Running: microk8s start or microk8s stop; microk8s start will not solve the issues
> Running: microk8s reset will also not solve the issue
> Running microk8s stop before the reboot seems to help, but still fails on some snap update
> Rebooting will also not solve the issue
> 
> This issue seems to happen at random. I can reboot once, or twice with no failed state. Once I get a failed state there is no way to recover unless microk8's is re-installed