openstack/kolla-ansible.git/ansible/roles/mariadb/tasks, branch stable/2026.1

Include CA for database TLS on MariaDB backup

2026-09-25T12:42:02+00:00

When database backend TLS was implemented [1], the CA was not set for Mariabackup configuration. [1] https://review.opendev.org/c/openstack/kolla-ansible/+/909912 Closes-bug: #2168443 Change-Id: I2d88af7c61bb609311a5f0a820a501d006f8e454 Signed-off-by: Seunghun Lee (cherry picked from commit 7c64ed9ff0509b4001d319f620d4bfe68ae9dfdb)

mariadb: Back up from the local database instance

2026-08-25T12:27:03+00:00

Mariabackup copies the data directory of mariadb_backup_host but connected through the load balancer, so backup_replica.sh could redirect it to another Galera member. The backup lock then applied to the wrong node, leaving the copied files unquiesced. Connect to api_interface_address and mariadb_port instead, and always use the local backup script. MariaDB 10.11.19 and 11.4.13 no longer tolerate the mismatch. mariadb_backup_target now has no effect, and full backups are named mysqlbackup-.qp.xbc.xbs.gz, as the restore docs describe. Closes-Bug: #2165011 Related-Bug: #2125124 Change-Id: I33ebd36c728ff50df8ebf13fc5af9882a0e71d23 Signed-off-by: Bartosz Bezak (cherry picked from commit f1f2702bbe812e285f0766a5787159ba92fdce8b)

Wait for slaves to sync before the recovery master restart.

2026-07-27T08:39:14+00:00

During mariadb_recovery, recover_cluster.yml starts the bootstrap node, starts the slave containers, and then recreates the master container to clear pc.bootstrap. The "Wait for slave MariaDB" task between those steps only waits for the service port to open, but a freshly started slave is still receiving its state transfer (SST then IST) at that point. The master restart is a Galera cluster membership change, and a membership change while a joiner is mid-IST makes the joiner abort with "IST didn't contain all write sets, expected last: N last received: N-1 ... node restart required". The joiner then drops to non-primary, self-leaves, and sits permanently wsrep-disconnected; nothing restarts it, and the Galera readiness check added by commit aed9d890 fails the recovery. Over the last 30 days this hit 16 of 954 mariadb scenario CI runs (1.7%), was terminal in every case, and accounts for about 30% of all failures in those jobs, across Debian, Ubuntu and Rocky. The Ubuntu failures are on MariaDB 11.4.12, which already contains the upstream fixes for MDEV-36621 and MDEV-39643, so this window has to be closed at the orchestration layer. Add a wait for every slave to report wsrep_local_state_comment Synced before the master restart, using the same defensive until pattern as the bootstrap WSREP sync wait. The retry budget is larger than the port waits because a slave may legitimately still be receiving an SST at this point. Prompt: Michael asked for a kerbside-patches patch fixing the mariadb_recovery IST race we diagnosed from the kolla-ansible 989612 gate failures, where the master restart during recovery races slaves that are still receiving state transfer. Assisted-By: Claude Fable 5 (200K context, medium effort) Co-Authored-By: Claude Fable 5 (200K context, medium effort) Closes-Bug: #2161773 Change-Id: Ifd0260fa4875051b1c38ee52de4f0de1806f6cc9 Signed-off-by: Michael Still (cherry picked from commit cb259a3914180234cef888ddfe34b54f60f240a0)

mariadb: add support for custom Galera notification script

2026-03-30T14:50:17+00:00

This patch adds the ability for operators to provide a custom wsrep-notify.sh script to handle Galera cluster events (e.g., node status changes, membership updates). If a script is placed in the custom configuration directory on the control host (/etc/kolla/config/mariadb/wsrep-notify.sh), Kolla Ansible will copy it to the nodes, mount it into the MariaDB container at /usr/local/bin/ and enable 'wsrep_notify_cmd'. This enables integration with external systems like Alertmanager or local logging without hardcoding scripts into the roles. Change-Id: I7887889cb2e4038baeb566884cb847a71b5f99a6 Signed-off-by: Piotr Milewski

ansible-lint: Fix fqcn[actions-core] for mariadb

2026-03-22T20:06:36+00:00

Change-Id: I1d918203cec028e6be17925044ce2a0d9e040276 Signed-off-by: Michal Nasiadka

Merge "Use mariadb command instead of mysql for upgrade"

2025-12-11T12:49:38+00:00

ansible-lint: fix unnamed-task in mariadb

2025-12-10T21:19:49+00:00

Change-Id: Ie6b3330a9d7587c233fbeef600b9035ede5b081a Signed-off-by: Bertrand Lanson

Use mariadb command instead of mysql for upgrade

2025-12-09T14:21:36+00:00

This fixes upgrades from 2025.2 to master, since 2025.2 images do not include the mysql binary anymore [1]. SLURP upgrades should still work, since 2025.1 images include both commands: $ ls -l /usr/bin/mariadb /usr/bin/mysql -rwxr-xr-x. 1 root root 5390512 Nov 3 13:25 /usr/bin/mariadb lrwxrwxrwx. 1 root root 7 Nov 3 13:25 /usr/bin/mysql -> mariadb [1] https://review.opendev.org/c/openstack/kolla/+/926981 Change-Id: Iccd0270ac3c0adbea56fbe3c8b80e1bb644c20c5 Signed-off-by: Pierre Riteau

Fix incorrect mariadb-recovery task name in error message

2025-12-06T03:39:28+00:00

Closes-Bug: #2133983 Change-Id: Ib79cd622123d9b6727ab1d674f680b8e2d52ed68 Signed-off-by: Vudn

ansible-lint: Fix name[template], remove package-latest

2025-12-04T15:36:11+00:00

Change-Id: I7c693403b1768c6c97eea90c3dfe9326764c3230 Signed-off-by: Michal Nasiadka