8a9127efbc
On a running galera cluster, we don't want to unintentionally allow a galera_cluster_name from changing. This will cause a cluster to fail to start (if the nodes are restarted sequentially) as the cluter name value has changed. To ensure we can still change this value, a new "galera_force_change_cluster_name" variable is added, which can be set to "True" in order to change the cluster name. Change-Id: I8bae038bd207a15d5731b9c91b78df851a4c1986
16 lines
735 B
YAML
16 lines
735 B
YAML
---
|
|
features:
|
|
- The ``openstack-ansible-galera_server`` role will now prevent
|
|
deployers from changing the ``galera_cluster_name`` variable
|
|
on clusters that already have a value set in a running galera
|
|
cluster.
|
|
You can set the new ``galera_force_change_cluster_name``
|
|
variable to ``True`` to force the ``galera_cluster_name``
|
|
variable to be changed.
|
|
We recommend setting this by running the galera-install.yml playbook
|
|
with ``-e galera_force_change_cluster_name=True``, to avoid
|
|
changing the ``galera_cluster_name`` variable unintentionally.
|
|
Use with caution, changing the ``galera_cluster_name`` value
|
|
can cause your cluster to fail, as the nodes won't join if restarted
|
|
sequentially.
|