From 9fee5107c24880c8365cc2c1905a804cb86ee770 Mon Sep 17 00:00:00 2001 From: Nicolas Bock Date: Wed, 26 Sep 2018 12:19:57 -0600 Subject: [PATCH] Enable the xinetd service for reboot If the Galera container is rebooted, the xinetd service should be started. Otherwise the haproxy health check will fail and haproxy will not forward database connections. Change-Id: Iefa7b72ea1fa6743fb8486af663512c2ffe1c31d --- handlers/main.yml | 1 + tasks/galera_post_install.yml | 9 +++++++++ 2 files changed, 10 insertions(+) diff --git a/handlers/main.yml b/handlers/main.yml index 58f653e4..a35446be 100644 --- a/handlers/main.yml +++ b/handlers/main.yml @@ -94,3 +94,4 @@ service: name: xinetd state: restarted + enabled: true diff --git a/tasks/galera_post_install.yml b/tasks/galera_post_install.yml index 0d3d34a1..807f713b 100644 --- a/tasks/galera_post_install.yml +++ b/tasks/galera_post_install.yml @@ -181,6 +181,15 @@ dest: "/usr/local/bin/clustercheck" mode: "0755" +# TODO: (nicolasbock) This task can be removed in T but is necessary +# for S and earlier because deployments prior to this change will not +# have the xinetd service enabled because the handler task runs only +# for new deployments. +- name: Enable xinetd service + service: + name: xinetd + enabled: yes + - name: Create mysqlchk config template: src: "mysqlchk.j2"