9f14ad651a
These affected both deploy (and reconfigure) and upgrade resulting in WSREP issues, failed deploys or need to recover the cluster. This patch makes sure k-a does not abruptly terminate nodes to break cluster. This is achieved by cleaner separation between stages (bootstrap, restart current, deploy new) and 3 phases for restarts (to keep the quorum). Upgrade actions, which operate on a healthy cluster, went to its section. Service restart was refactored. We no longer rely on the master/slave distinction as all nodes are masters in Galera. Closes-bug: #1857908 Closes-bug: #1859145 Change-Id: I83600c69141714fc412df0976f49019a857655f5
18 lines
820 B
YAML
18 lines
820 B
YAML
---
|
|
fixes:
|
|
- |
|
|
Fixes MariaDB issues in multinode scenarios which affected
|
|
deployment, reconfiguration, upgrade and Galera cluster resizing.
|
|
They were usually manifested by WSREP issues in various places
|
|
and could lead to need to recover the Galera cluster.
|
|
Note these issues were due to how MariaDB was handled during
|
|
Kolla Ansible runs and did not affect Galera cluster during normal
|
|
operations unless MariaDB was later touched by Kolla Ansible.
|
|
Users wishing to run actions on their Galera clusters using
|
|
Kolla Ansible are strongly advised to update.
|
|
For details please see the following Launchpad bug records:
|
|
`bug 1857908
|
|
<https://bugs.launchpad.net/kolla-ansible/+bug/1857908>`__ and
|
|
`bug 1859145
|
|
<https://bugs.launchpad.net/kolla-ansible/+bug/1859145>`__.
|