Configure galera-monitor on all controller nodes
When we implemented the galera composable role we accidentally moved the xinetd.d monitor service on the bootstrap node only. This meant that haproxy believed that galera was down on the non-bootstrap nodes. A shutdown of the bootstrap node meant that galera was effectively down because haproxy would refuse to redirect the traffic to the non-bootstrap node. Fix this by creating the /etc/xinetd.d/galera-monitor on all controller nodes. Change-Id: Ib5a06b3abbc32182476c2b0c81eb77a12821ad6b
This commit is contained in:
parent
a805daefd1
commit
2cbbe14a76
@ -71,7 +71,7 @@ class tripleo::profile::pacemaker::database::mysql (
|
||||
mysql_server_options => $mysqld_options,
|
||||
}
|
||||
|
||||
if $step >= 2 and $pacemaker_master {
|
||||
if $step >= 2 {
|
||||
if $pacemaker_master {
|
||||
pacemaker::resource::ocf { 'galera' :
|
||||
ocf_agent_name => 'heartbeat:galera',
|
||||
|
Loading…
x
Reference in New Issue
Block a user