Hi everybody,
I'm having a problem when my HA database, topology

Here is the configuration in the galera cluster:
[galera]
binlog_format = ROW
default-storage-engine = innodb
innodb_autoinc_lock_mode = 2
bind-address = 0.0.0.0
wsrep_on = ON
wsrep_provider = / usr / lib64 / galera / libgalera_smm.so
wsrep_cluster_address = "gcomm: //
10.120.190.61,10.120.190.62,10.120.190.63"
## Galera Cluster Configuration
wsrep_cluster_name = "galera"
## Galera Synchronization Configuration
wsrep_sst_method = rsync
## Galera Node Configuration
wsrep_node_address = "10.120.190.61"
wsrep_node_name = "DB1"
The galera cluster was able to sync well, but my problem is: when I create resource galera for pacemaker then pacemaker cannot be promoted master
Here is my pacemaker setup:
#yum -y install pacemaker pcs
#pcs property set stonith-enabled = false
#pcs property set no-quorum-policy = ignore
#pcs property set default-resource-stickiness = "INFINITY"
#pcs resource create Virtual_IP ocf: heartbeat: IPaddr2 ip = 10.123.70.60 cidr_netmask = 24 op monitor interval = 30s
#pcs resource create p_galera ocf: heartbeat: galera \
wsrep_cluster_address = gcomm: // DB1, DB2, DB3 \
op monitor depth = "0" timeout = "30s" interval = "20s" \
op monitor role = "Master" depth = "0" timeout = "30s" interval = "10s" \
op monitor role = "Slave" depth = "0" timeout = "30s" interval = "30s" --master
Error:
"resource is master / slave but has not been promoted to master on any node"
I didn't disable the mariadb service when adding galera to pacemaker, but I tried disabling mariadb and still failed
Please help me, I am using centos 7.8 and mariadb 10.3.27, pacemaker 0.10.6
Thanks very much!