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
(cherry picked from commit 9fee5107c2
)
This commit is contained in:
parent
efa513980f
commit
dc3b809071
|
@ -61,3 +61,4 @@
|
|||
service:
|
||||
name: xinetd
|
||||
state: restarted
|
||||
enabled: true
|
||||
|
|
|
@ -133,6 +133,15 @@
|
|||
tags:
|
||||
- galera-config
|
||||
|
||||
# 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"
|
||||
|
|
Loading…
Reference in New Issue