Instance High Availability (High Availability for Compute Instances) - all stonith resources in Stopped state when deploying with one controller in Red Hat OpenStack Platform 13

Issue

• Instance High Availability (High Availability for Compute Instances) is deployed with one controller only
• All stonith resources are in Stopped state

[root@controller-0 ~]# pcs status
Cluster name: tripleo_cluster
Stack: corosync
Current DC: controller-0 (version 1.1.19-8.el7-c3c624ea3d) - partition with quorum
Last updated: Fri Nov 16 22:44:43 2018
Last change: Fri Nov 16 22:43:14 2018 by compute-1 via cibadmin on controller-0

8 nodes configured
36 resources configured

Online: [ controller-0 ]
RemoteOnline: [ compute-0 compute-1 compute-2 compute-3 ]
GuestOnline: [ galera-bundle-0@controller-0 rabbitmq-bundle-0@controller-0 redis-bundle-0@controller-0 ]

Full list of resources:

 compute-0      (ocf::pacemaker:remote):        Started controller-0
 compute-1      (ocf::pacemaker:remote):        Started controller-0
 compute-2      (ocf::pacemaker:remote):        Started controller-0
 compute-3      (ocf::pacemaker:remote):        Started controller-0
 Docker container: rabbitmq-bundle [192.168.100.1:8787/rhosp13/openstack-rabbitmq:pcmklatest]
   rabbitmq-bundle-0    (ocf::heartbeat:rabbitmq-cluster):      Started controller-0
 Docker container: galera-bundle [192.168.100.1:8787/rhosp13/openstack-mariadb:pcmklatest]
   galera-bundle-0      (ocf::heartbeat:galera):        Master controller-0
 Docker container: redis-bundle [192.168.100.1:8787/rhosp13/openstack-redis:pcmklatest]
   redis-bundle-0       (ocf::heartbeat:redis): Master controller-0
 ip-192.168.100.16      (ocf::heartbeat:IPaddr2):       Started controller-0
 ip-192.168.92.10       (ocf::heartbeat:IPaddr2):       Started controller-0
 ip-10.20.60.54 (ocf::heartbeat:IPaddr2):       Started controller-0
 ip-10.20.60.59 (ocf::heartbeat:IPaddr2):       Started controller-0
 ip-10.20.70.51 (ocf::heartbeat:IPaddr2):       Started controller-0
 ip-10.20.100.57        (ocf::heartbeat:IPaddr2):       Started controller-0
 Docker container: haproxy-bundle [192.168.100.1:8787/rhosp13/openstack-haproxy:pcmklatest]
   haproxy-bundle-docker-0      (ocf::heartbeat:docker):        Started controller-0
 stonith-fence_compute-fence-nova       (stonith:fence_compute):        Stopped
 Clone Set: compute-unfence-trigger-clone [compute-unfence-trigger]
     Started: [ compute-0 compute-1 compute-2 compute-3 ]
     Stopped: [ controller-0 ]
 nova-evacuate  (ocf::openstack:NovaEvacuate):  Started controller-0
 stonith-fence_ipmilan-941882650e48     (stonith:fence_ipmilan):        Stopped
 Docker container: openstack-cinder-volume [192.168.100.1:8787/rhosp13/openstack-cinder-volume:pcmklatest]
   openstack-cinder-volume-docker-0     (ocf::heartbeat:docker):        Started controller-0
 stonith-fence_ipmilan-98f2b326a428     (stonith:fence_ipmilan):        Stopped
 stonith-fence_ipmilan-f403435ce788     (stonith:fence_ipmilan):        Stopped
 stonith-fence_ipmilan-98f2b325ce4c     (stonith:fence_ipmilan):        Stopped
 stonith-fence_ipmilan-94188265065c     (stonith:fence_ipmilan):        Stopped

Daemon Status:
  corosync: active/enabled
  pacemaker: active/enabled
  pcsd: active/enabled
[root@controller-0 ~]#

• when settings stonith-enabled to false, stonith resources go to started:

pcs property set stonith-enabled=false

• pcs stonith fence <compute node> will fence the compute node, but the node is never unfenced and does not come back online until stonith-enabled is set to false