You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After the hypervisor is rebooted the master and workers nodes are down
$ sudo virsh list --all
Id Name State
----------------------------------------------------
- openshift_master_0 shut off
- openshift_master_1 shut off
- openshift_master_2 shut off
- openshift_worker_0 shut off
$ sudo podman ps -a
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
e7759c11b703 quay.io/metalkube/metalkube-ironic-inspector:latest /bin/runironic-in... 2 hours ago Exited (143) 18 minutes ago ironic-inspector
f88ab5919b44 quay.io/metalkube/metalkube-ironic:latest /bin/runironic 2 hours ago Exited (143) 18 minutes ago ironic
ac96c6b1f735 quay.io/metalkube/metalkube-ironic:latest /bin/runmariadb 2 hours ago Exited (0) 18 minutes ago mariadb
35bc2d03feff quay.io/metalkube/metalkube-ironic:latest /bin/runhttpd 2 hours ago Exited (143) 18 minutes ago httpd
e7c55f77b63a quay.io/metalkube/metalkube-ironic:latest /bin/rundnsmasq 2 hours ago Exited (143) 18 minutes ago dnsmasq
214443a07343 k8s.gcr.io/pause:3.1
To Reproduce
After installation and verifying that the cluster is up reboot the hypervisor and check that the cluster is down.
Expected/observed behaviour
The cluster should be functional after the reboot of the hypervisor
The text was updated successfully, but these errors were encountered:
Note that rebooting the host isn't recommended as you'll probably run into #374 afterwards, when that is fixed (a podman/libpod bug) we can perhaps revisit this and ensure the VMs/pod are auto-started on reboot.
Yeah, I'd say this is either "won't fix" or at least very low priority since this is a short term dev/test environment, not a production thing that needs to survive reboots.
After the hypervisor is rebooted the master and workers nodes are down
To Reproduce
After installation and verifying that the cluster is up reboot the hypervisor and check that the cluster is down.
Expected/observed behaviour
The cluster should be functional after the reboot of the hypervisor
The text was updated successfully, but these errors were encountered: