Using galera_my_cnf_overrides brakes cluster config
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack-Ansible |
Fix Released
|
High
|
Miguel Alejandro Cantu |
Bug Description
TL;DR: When using galera_
I discovered that while troubleshooting a galera setup problem, where I used galera_
galera_
sst:
sst-
Only to find that it made the problem even worse. After some further troubleshooting I realized that something removed a quiet important line from my my.cnf in the galera lxc container. The line that is missing is:
!includedir /etc/mysql/conf.d/
Which will include other configuration files including those used by wsrep. Bootstrapping a new galera cluster obviously will not work if this line is missing, I have no idea what that change would do to an existing cluster...
The corresponding task can be found in /etc/ansible/
- name: Drop mariadb config(s)
config_template:
src: "{{ item.src }}"
dest: "{{ item.dest }}"
owner: "root"
group: "root"
mode: "0644"
config_
config_type: "{{ item.config_type }}"
with_items:
- src: my.cnf.j2
dest: /etc/mysql/my.cnf
config_
config_type: "ini"
- src: cluster.cnf.j2
dest: /etc/mysql/
config_
config_type: "ini"
- src: debian.cnf.j2
dest: /etc/mysql/
config_
config_type: "ini"
notify: Restart mysql
tags:
- galera-config
- galera-
For me it looks like the "!includedir " line is treated as an comment and gets removed by the config_template module.
summary: |
- Using galera_my_cnf_overrides removes includedir line + Using galera_my_cnf_overrides brakes cluster config |
description: | updated |
description: | updated |
There is indeed a gap in our testing, which doesn't include a test of "!".
It should work by default, but we'll confirm it when we include this testing.
Marking as confirmed for that reason.