From 52353e37711f1be4b39828d62e97cfa7edf8c7d7 Mon Sep 17 00:00:00 2001
From: Dmitriy Rabotyagov <dmitriy.rabotyagov@cleura.com>
Date: Tue, 18 Jul 2023 11:34:58 +0200
Subject: [PATCH] Do not use notify inside handlers

Since latest ansible handlers are not triggered inside the same
handlers flush, which means that triggering mysql restart
the way we did does not work anymore. So instead of
notifying inside handlers, we add listen key to tasks
that are triggered by these newly produced notifications.

This could be due to the bug [1], but ansible-core version that has
backport included still shows inconsistent behaviour

[1] https://github.com/ansible/ansible/issues/80880

Change-Id: If188ef9ef978332dc94b282893140de572bac6f3
---
 handlers/main.yml | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/handlers/main.yml b/handlers/main.yml
index acb38a2..2a0ae84 100644
--- a/handlers/main.yml
+++ b/handlers/main.yml
@@ -17,7 +17,6 @@
   shell: >-
     cat {{ zookeeper_ssl_cert }} $(test -f {{ zookeeper_ssl_ca_cert }} &&
       echo {{ zookeeper_ssl_ca_cert }}) {{ zookeeper_ssl_key }} > {{ zookeeper_ssl_keystore_location }}
-  notify: Restart zookeeper
   listen:
     - cert installed
 
@@ -28,6 +27,7 @@
   listen:
     - Restart zookeeper
     - systemd service changed
+    - cert installed
 
 - name: Symlink zookeeper
   file:
@@ -46,3 +46,4 @@
   listen:
     - Restart zookeeper
     - systemd service changed
+    - cert installed