kubernetes is not alive after rebooting host

Bug #2027866 reported by Yasufumi Ogawa
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
kuryr-kubernetes
Won't Fix
Undecided
Unassigned

Bug Description

I'm using the latest kuryr-kubernetes deployed with devstack on Ubuntu22.04 VM and k8s works fine. However, it's not running after rebooting the VM.

```
$ kubectl get nodes
The connection to the server 192.168.56.11:6443 was refused - did you specify the right host or port?
```

There is a failure occurred while launching kubelet from systemctl.

```
$ systemctl status kubelet
● kubelet.service - kubelet: The Kubernetes Node Agent
     Loaded: loaded (/lib/systemd/system/kubelet.service; enabled; vendor preset: enabled)
    Drop-In: /etc/systemd/system/kubelet.service.d
             └─10-kubeadm.conf
     Active: activating (auto-restart) (Result: exit-code) since Sat 2023-07-15 19:05:39 UTC; 3s ago
       Docs: https://kubernetes.io/docs/home/
    Process: 70935 ExecStart=/usr/bin/kubelet $KUBELET_KUBECONFIG_ARGS $KUBELET_CONFIG_ARGS $KUBELET_KUBEADM_ARGS $KUBELET_EXTRA_ARGS (code=exited, status=1/FAILURE)
   Main PID: 70935 (code=exited, status=1/FAILURE)
        CPU: 81ms
```

Revision history for this message
Michal Dulko (michal-dulko-f) wrote :

DevStack is not designed to survive a reboot of the machine. This use case is simply not supported.

Changed in kuryr-kubernetes:
status: New → Won't Fix
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.