| 2017-05-24 13:58:09 |
Daniel Marks |
bug |
|
|
added bug |
| 2017-05-24 14:33:06 |
Daniel Marks |
summary |
Using galera_my_cnf_overrides removes includedir line |
Using galera_my_cnf_overrides brakes cluster config |
|
| 2017-05-30 07:42:36 |
Daniel Marks |
description |
While troubleshooting a galera setup problem I used galera_my_cnf_overrides in my user_variables.
galera_my_cnf_overrides:
sst:
sst-initial-timeout: 600
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 galer 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/roles/galera_server/tasks/galera_post_install.yml
- name: Drop mariadb config(s)
config_template:
src: "{{ item.src }}"
dest: "{{ item.dest }}"
owner: "root"
group: "root"
mode: "0644"
config_overrides: "{{ item.config_overrides }}"
config_type: "{{ item.config_type }}"
with_items:
- src: my.cnf.j2
dest: /etc/mysql/my.cnf
config_overrides: "{{ galera_my_cnf_overrides }}"
config_type: "ini"
- src: cluster.cnf.j2
dest: /etc/mysql/conf.d/cluster.cnf
config_overrides: "{{ galera_cluster_cnf_overrides }}"
config_type: "ini"
- src: debian.cnf.j2
dest: /etc/mysql/debian.cnf
config_overrides: "{{ galera_debian_cnf_overrides }}"
config_type: "ini"
notify: Restart mysql
tags:
- galera-config
- galera-client-user-config
For me it looks like the "!includedir " line is treated as an comment and gets removed by the config_template module. |
TL;DR: When using galera_my_cnf_overrides the includedir line in my.cnf is treated as a comment and gets removed from the config_template module.
I discovered that while troubleshooting a galera setup problem, where I used galera_my_cnf_overrides in my user_variables.
galera_my_cnf_overrides:
sst:
sst-initial-timeout: 600
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/roles/galera_server/tasks/galera_post_install.yml
- name: Drop mariadb config(s)
config_template:
src: "{{ item.src }}"
dest: "{{ item.dest }}"
owner: "root"
group: "root"
mode: "0644"
config_overrides: "{{ item.config_overrides }}"
config_type: "{{ item.config_type }}"
with_items:
- src: my.cnf.j2
dest: /etc/mysql/my.cnf
config_overrides: "{{ galera_my_cnf_overrides }}"
config_type: "ini"
- src: cluster.cnf.j2
dest: /etc/mysql/conf.d/cluster.cnf
config_overrides: "{{ galera_cluster_cnf_overrides }}"
config_type: "ini"
- src: debian.cnf.j2
dest: /etc/mysql/debian.cnf
config_overrides: "{{ galera_debian_cnf_overrides }}"
config_type: "ini"
notify: Restart mysql
tags:
- galera-config
- galera-client-user-config
For me it looks like the "!includedir " line is treated as an comment and gets removed by the config_template module. |
|
| 2017-05-30 07:42:56 |
Daniel Marks |
description |
TL;DR: When using galera_my_cnf_overrides the includedir line in my.cnf is treated as a comment and gets removed from the config_template module.
I discovered that while troubleshooting a galera setup problem, where I used galera_my_cnf_overrides in my user_variables.
galera_my_cnf_overrides:
sst:
sst-initial-timeout: 600
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/roles/galera_server/tasks/galera_post_install.yml
- name: Drop mariadb config(s)
config_template:
src: "{{ item.src }}"
dest: "{{ item.dest }}"
owner: "root"
group: "root"
mode: "0644"
config_overrides: "{{ item.config_overrides }}"
config_type: "{{ item.config_type }}"
with_items:
- src: my.cnf.j2
dest: /etc/mysql/my.cnf
config_overrides: "{{ galera_my_cnf_overrides }}"
config_type: "ini"
- src: cluster.cnf.j2
dest: /etc/mysql/conf.d/cluster.cnf
config_overrides: "{{ galera_cluster_cnf_overrides }}"
config_type: "ini"
- src: debian.cnf.j2
dest: /etc/mysql/debian.cnf
config_overrides: "{{ galera_debian_cnf_overrides }}"
config_type: "ini"
notify: Restart mysql
tags:
- galera-config
- galera-client-user-config
For me it looks like the "!includedir " line is treated as an comment and gets removed by the config_template module. |
TL;DR: When using galera_my_cnf_overrides the includedir line in my.cnf is treated as a comment and gets removed by the config_template module.
I discovered that while troubleshooting a galera setup problem, where I used galera_my_cnf_overrides in my user_variables.
galera_my_cnf_overrides:
sst:
sst-initial-timeout: 600
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/roles/galera_server/tasks/galera_post_install.yml
- name: Drop mariadb config(s)
config_template:
src: "{{ item.src }}"
dest: "{{ item.dest }}"
owner: "root"
group: "root"
mode: "0644"
config_overrides: "{{ item.config_overrides }}"
config_type: "{{ item.config_type }}"
with_items:
- src: my.cnf.j2
dest: /etc/mysql/my.cnf
config_overrides: "{{ galera_my_cnf_overrides }}"
config_type: "ini"
- src: cluster.cnf.j2
dest: /etc/mysql/conf.d/cluster.cnf
config_overrides: "{{ galera_cluster_cnf_overrides }}"
config_type: "ini"
- src: debian.cnf.j2
dest: /etc/mysql/debian.cnf
config_overrides: "{{ galera_debian_cnf_overrides }}"
config_type: "ini"
notify: Restart mysql
tags:
- galera-config
- galera-client-user-config
For me it looks like the "!includedir " line is treated as an comment and gets removed by the config_template module. |
|
| 2017-05-30 16:26:53 |
Jean-Philippe Evrard |
openstack-ansible: status |
New |
Confirmed |
|
| 2017-05-30 16:26:56 |
Jean-Philippe Evrard |
openstack-ansible: importance |
Undecided |
High |
|
| 2017-06-20 15:10:22 |
Miguel Alejandro Cantu |
openstack-ansible: assignee |
|
Miguel Alejandro Cantu (miguel-cantu) |
|
| 2017-06-23 19:35:57 |
OpenStack Infra |
openstack-ansible: status |
Confirmed |
In Progress |
|
| 2017-06-27 21:00:44 |
OpenStack Infra |
openstack-ansible: status |
In Progress |
Fix Released |
|
| 2017-08-22 12:14:51 |
OpenStack Infra |
tags |
|
in-stable-ocata |
|
