with cengn "20190604T144018Z", once "reboot -f",active host switch to controller-1 , but some pods are abnormal. need further check why pod has Error [wrsroot@controller-1 ~(keystone_admin)]$ kubectl get pods -n openstack | grep Error aodh-api-65d447f66d-ct77l 0/1 Error 0 54m aodh-evaluator-77d464bb74-6x92j 0/1 Error 0 54m aodh-listener-9dfb8f677-6zjsm 0/1 Error 0 54m aodh-notifier-5cd9f88587-fd5zr 0/1 Error 0 54m barbican-api-7fdd595748-fp89v 0/1 Error 0 74m cinder-backup-786c58bd79-hh6hh 0/1 Error 0 57m cinder-scheduler-7c5ddf9976-zjffc 0/1 Error 0 57m cinder-volume-b6cbbb476-ksjkl 0/1 Error 0 57m glance-api-99c864d6f-x298r 0/1 Error 0 73m gnocchi-api-55798d5b5b-xgzwd 0/1 Error 0 52m gnocchi-metricd-dxnv9 0/1 Error 0 52m heat-api-858945db9f-g9cpk 0/1 Error 0 61m heat-engine-56bd4c9bc9-xwrhc 0/1 Error 0 61m keystone-api-bf59bb9f6-bnbqw 0/1 Error 0 77m libvirt-libvirt-default-2nhj5 0/1 Error 0 70m neutron-dhcp-agent-controller-0-9626473e-mh9z8 0/1 Error 0 70m neutron-metadata-agent-controller-0-a762cb46-x9f65 0/1 Error 0 70m neutron-server-5cfdcd846c-j7vbm 0/1 Error 0 70m nova-api-metadata-6d9b66759b-g2sbm 0/1 Error 1 70m nova-api-osapi-6db69588f5-6gcdg 0/1 Error 0 70m nova-api-proxy-6ff4c8f7c7-xqjzx 0/1 Error 0 70m nova-compute-controller-0-dec13249-cp46z 0/2 Error 0 70m nova-conductor-7bffdff5dd-s4trs 0/1 Error 0 70m nova-novncproxy-5fb4d6958d-tvwqs 0/1 Error 0 70m nova-placement-api-799489447d-v8prf 0/1 Error 0 70m openvswitch-db-ngc5r 0/1 Error 0 70m openvswitch-vswitchd-t9ztn 0/1 Error 0 70m osh-openstack-rabbitmq-rabbitmq-0 0/1 Error 0 79m panko-api-5f66468d49-pxfgx 0/1 Error 0 50m after a while, the pods get normal, and controller-1:~$ openstack server list +--------------------------------------+------+--------+---------------------+--------+----------+ | ID | Name | Status | Networks | Image | Flavor | +--------------------------------------+------+--------+---------------------+--------+----------+ | df91f4c5-7209-4a3b-bde4-a2b878e84b1a | vm1 | ACTIVE | net=192.168.100.240 | cirros | m1.tinny | | 8c81b0bc-61e8-4248-80f2-159037e53e58 | vm0 | ACTIVE | net=192.168.100.22 | cirros | m1.tinny | +--------------------------------------+------+--------+---------------------+--------+----------+ controller-1:~$ openstack h help host hypervisor controller-1:~$ openstack hypervisor list +----+---------------------+-----------------+---------------+-------+ | ID | Hypervisor Hostname | Hypervisor Type | Host IP | State | +----+---------------------+-----------------+---------------+-------+ | 4 | controller-1 | QEMU | 192.168.206.4 | up | | 6 | controller-0 | QEMU | 192.168.206.3 | up | +----+---------------------+-----------------+---------------+-------+ The only issue should be alarm is not clean-up 270.001 | Host controller-0 compute services failure, | host=controller-0. | critical | 2019-06-11T08 | | | | services=compute | | :51:32.435431 | need check how to clear up this fm alarm