commit f979ae1f8ee182a8bc6fde4b23b95a460cb81488
Author: Mark Goddard <email address hidden>
Date: Thu Nov 7 10:01:14 2019 +0000
Fix restart policy after MariaDB recovery
After performing a recovery of MariaDB, the mariadb containers are left
without a restart policy. This leaves them unable to recover from the
crash of a single galera node. There is another issue, in that the
'master' node is left in a bootstrap configuration, with the
--wsrep-new-cluster argument configured as BOOTSTRAP_ARGS.
This change fixes these issues by removing the restart policy of 'no'
from the 'slave' containers, and recreating the master container without
the restart policy or bootstrap arguments.
Reviewed: https:/ /review. opendev. org/693329 /git.openstack. org/cgit/ openstack/ kolla-ansible/ commit/ ?id=f979ae1f8ee 182a8bc6fde4b23 b95a460cb81488
Committed: https:/
Submitter: Zuul
Branch: master
commit f979ae1f8ee182a 8bc6fde4b23b95a 460cb81488
Author: Mark Goddard <email address hidden>
Date: Thu Nov 7 10:01:14 2019 +0000
Fix restart policy after MariaDB recovery
After performing a recovery of MariaDB, the mariadb containers are left new-cluster argument configured as BOOTSTRAP_ARGS.
without a restart policy. This leaves them unable to recover from the
crash of a single galera node. There is another issue, in that the
'master' node is left in a bootstrap configuration, with the
--wsrep-
This change fixes these issues by removing the restart policy of 'no'
from the 'slave' containers, and recreating the master container without
the restart policy or bootstrap arguments.
Change-Id: I36c87561193116 3ca2c29ae93b71d 3af64cb197c
Closes-Bug: #1851594