From ee8a3f52a3b66233b764b8402ae9703d578475d9 Mon Sep 17 00:00:00 2001 From: Michal Nasiadka Date: Tue, 7 Jul 2026 19:37:06 +0200 Subject: mariadb: Increase healthcheck start_period to 120s MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit On fresh deployments the monitor user is created in post-deploy, after containers have started — with the default 5s start_period the first healthcheck fires at t+30s (interval) before the user exists. 120s also provides enough margin for SST on larger databases. Change-Id: Ia415f49a5486920426a09509af9df2d436c2d4a8 Signed-off-by: Michal Nasiadka (cherry picked from commit 43d67f0475e8ea4fb2d11e1147fba06dbf22e6b6) --- ansible/roles/mariadb/defaults/main.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/ansible/roles/mariadb/defaults/main.yml b/ansible/roles/mariadb/defaults/main.yml index d1023f846..8fac5f8b6 100644 --- a/ansible/roles/mariadb/defaults/main.yml +++ b/ansible/roles/mariadb/defaults/main.yml @@ -55,7 +55,7 @@ mariadb_extra_volumes: "{{ default_extra_volumes }}" mariadb_enable_healthchecks: "{{ enable_container_healthchecks }}" mariadb_healthcheck_interval: "{{ default_container_healthcheck_interval }}" mariadb_healthcheck_retries: "{{ default_container_healthcheck_retries }}" -mariadb_healthcheck_start_period: "{{ default_container_healthcheck_start_period }}" +mariadb_healthcheck_start_period: 120 mariadb_healthcheck_test: - "CMD-SHELL" - >- -- cgit v1.2.3