Deploy OpenStack HA Cluster automatically based on the two books "Openstack Cluster HA:Deployment and Operation" and "Openstack Cluster HA:Architecture and Principles"
[root@controller1 ~]# pcs status
Cluster name: openstack-ha
Stack: corosync
Current DC: controller1 (version 1.1.19-8.el7_6.4-c3c624ea3d) - partition with quorum
Last updated: Tue May 7 16:52:46 2019
Last change: Tue May 7 16:47:13 2019 by root via cibadmin on controller1
3 nodes configured
18 resources configured
Online: [ controller1 controller2 controller3 ]
Full list of resources:
Clone Set: lb-haproxy-clone [lb-haproxy]
Started: [ controller1 controller2 controller3 ]
vip-db (ocf::heartbeat:IPaddr2): Started controller1
vip-rabbitmq (ocf::heartbeat:IPaddr2): Started controller2
vip-keystone (ocf::heartbeat:IPaddr2): Started controller3
vip-glance (ocf::heartbeat:IPaddr2): Started controller1
vip-cinder (ocf::heartbeat:IPaddr2): Started controller2
vip-swift (ocf::heartbeat:IPaddr2): Started controller3
vip-neutron (ocf::heartbeat:IPaddr2): Started controller1
vip-nova (ocf::heartbeat:IPaddr2): Started controller2
vip-horizon (ocf::heartbeat:IPaddr2): Started controller3
vip-heat (ocf::heartbeat:IPaddr2): Started controller1
vip-ceilometer (ocf::heartbeat:IPaddr2): Started controller2
vip-qpid (ocf::heartbeat:IPaddr2): Started controller3
Master/Slave Set: galera-master [galera]
Stopped: [ controller1 controller2 controller3 ]
Failed Actions:
galera_start_0 on controller2 'unknown error' (1): call=172, status=complete, exitreason='Unable to detect last known write sequence number',
last-rc-change='Tue May 7 16:43:53 2019', queued=0ms, exec=3173ms
galera_start_0 on controller3 'unknown error' (1): call=172, status=complete, exitreason='Unable to detect last known write sequence number',
last-rc-change='Tue May 7 16:43:57 2019', queued=1ms, exec=3173ms
galera_start_0 on controller1 'unknown error' (1): call=172, status=complete, exitreason='Unable to detect last known write sequence number',
last-rc-change='Tue May 7 16:43:50 2019', queued=0ms, exec=2944ms
[root@controller1 ~]# pcs status Cluster name: openstack-ha Stack: corosync Current DC: controller1 (version 1.1.19-8.el7_6.4-c3c624ea3d) - partition with quorum Last updated: Tue May 7 16:52:46 2019 Last change: Tue May 7 16:47:13 2019 by root via cibadmin on controller1
3 nodes configured 18 resources configured
Online: [ controller1 controller2 controller3 ]
Full list of resources:
Clone Set: lb-haproxy-clone [lb-haproxy] Started: [ controller1 controller2 controller3 ] vip-db (ocf::heartbeat:IPaddr2): Started controller1 vip-rabbitmq (ocf::heartbeat:IPaddr2): Started controller2 vip-keystone (ocf::heartbeat:IPaddr2): Started controller3 vip-glance (ocf::heartbeat:IPaddr2): Started controller1 vip-cinder (ocf::heartbeat:IPaddr2): Started controller2 vip-swift (ocf::heartbeat:IPaddr2): Started controller3 vip-neutron (ocf::heartbeat:IPaddr2): Started controller1 vip-nova (ocf::heartbeat:IPaddr2): Started controller2 vip-horizon (ocf::heartbeat:IPaddr2): Started controller3 vip-heat (ocf::heartbeat:IPaddr2): Started controller1 vip-ceilometer (ocf::heartbeat:IPaddr2): Started controller2 vip-qpid (ocf::heartbeat:IPaddr2): Started controller3 Master/Slave Set: galera-master [galera] Stopped: [ controller1 controller2 controller3 ]
Failed Actions:
Daemon Status: corosync: active/enabled pacemaker: active/enabled pcsd: active/enabled
按照书本介绍的方式:pcs resource create galera galera enable_creation=true wsrep_cluster_address="gcomm://controller1,controller2,controller3" additional_parameters='--open-files-limit=16384' meta master-max=3 ordered=true op promote timeout=300s on-fail=block --master 出现上面的错误,mariadb galera启动不了,可否指点