Routing broken following Ubuntu 21.10 Upgrade

I was previously running v1.19 under Ubuntu 21.04 without issue, but following upgrade to 21.10 the cluster was pretty much hosed. Since then I’ve both microk8s reset and snap remove microk8s and installed the current edge release (v1.22.3).

The cluster starts but the calico controller gets into a Crash Loop with errors like:

2021-11-04 12:32:04.139 [INFO][1] main.go 88: Loaded configuration from environment config=&config.Config{LogLevel:"info", WorkloadEndpointWorkers:1, ProfileWorkers:1, PolicyWorkers:1, NodeWorkers:1, Kubeconfig:"", DatastoreType:"kubernetes"}
W1104 12:32:04.140304       1 client_config.go:543] Neither --kubeconfig nor --master was specified.  Using the inClusterConfig.  This might not work.
2021-11-04 12:32:04.140 [INFO][1] main.go 109: Ensuring Calico datastore is initialized
2021-11-04 12:32:07.208 [ERROR][1] client.go 261: Error getting cluster information config ClusterInformation="default" error=Get "https://10.152.183.1:443/apis/crd.projectcalico.org/v1/clusterinformations/default": dial tcp 10.152.183.1:443: connect: no route to host
2021-11-04 12:32:07.208 [FATAL][1] main.go 114: Failed to initialize Calico datastore error=Get "https://10.152.183.1:443/apis/crd.projectcalico.org/v1/clusterinformations/default": dial tcp 10.152.183.1:443: connect: no route to host

If I try running any extensions (which I realise is a bit pointless while calico is broken) I see similar “no route to host” errors from pods trying to contact the Kube API.

I’m pretty much lost at this point. I suspect this may have something to do with cgroups2 but I’m speculating. Any advice on troubleshooting this would be much appreciated.

inspection-report-20211104_123715.tar.gz

[remartens]

I had the same issue after upgrading my Raspberry PI to Ubuntu 21.10. When I looked at the installation steps again to reinstall MicroK8S, I noticed the following note:

On Ubuntu 21.10: Install extra kernel modules with sudo apt install linux-modules-extra-raspi and restart MicroK8s with sudo microk8s stop; sudo microk8s start.

Installing the extra Linux kernel modules fixed it for me.

[stale[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.