Skip to content
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

After Hypervisor is rebooted the nodes and the containers on the hypervisor are down #540

Closed
itzikb-redhat opened this issue May 16, 2019 · 3 comments

Comments

@itzikb-redhat
Copy link

itzikb-redhat commented May 16, 2019

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

@hardys
Copy link

hardys commented May 17, 2019

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.

@russellb
Copy link
Member

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.

@russellb
Copy link
Member

decided to close as won't fix

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants