Details
-
Task
-
Status: Open (View Workflow)
-
Major
-
Resolution: Unresolved
-
None
-
None
Description
Hi guys.
I have a Galera basic 3-node cluster set up with TLS and if I use:
[sst]
tkey = /etc/my.cnf.d/certs/sst/sst.key
tcert = /etc/my.cnf.d/certs/sst/sst.crt
cluster will not bootstrap.
If I skip tkey & tcert cluster will start just fine and then I can on each node, one by one, put those options back in and restart the node and each node will restart, which will result in the cluster, allegedly, having SST with TLS.
I do not suppose this is desired nor expected behaviour thus I'm filing this bug report.
This reproduces easily and every time.
I'm on CentOS Stream with:
-> $ rpm -qa mariad* | sort
mariadb-10.3.27-3.module_el8.3.0+599+c587b2e7.x86_64
mariadb-backup-10.3.27-3.module_el8.3.0+599+c587b2e7.x86_64
mariadb-common-10.3.27-3.module_el8.3.0+599+c587b2e7.x86_64
mariadb-connector-c-3.1.11-2.el8_3.x86_64
mariadb-connector-c-config-3.1.11-2.el8_3.noarch
mariadb-errmsg-10.3.27-3.module_el8.3.0+599+c587b2e7.x86_64
mariadb-server-10.3.27-3.module_el8.3.0+599+c587b2e7.x86_64
mariadb-server-galera-10.3.27-3.module_el8.3.0+599+c587b2e7.x86_64
mariadb-server-utils-10.3.27-3.module_el8.3.0+599+c587b2e7.x86_64