From 98e86ea62b64eb1c5a7dfaca6c366527f584afc0 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Rados=C5=82aw=20Piliszek?= <radoslaw.piliszek@gmail.com>
Date: Sun, 26 Apr 2020 19:59:26 +0200
Subject: [PATCH] Remove redundant listen on haproxy handler
Follow-up on [1] "Avoid multiple haproxy restarts after
reconfiguration".
There is no need to duplicate handler name in listen.
The issue was because we had two handlers with the same
name in the same environment.
This causes Ansible not to mark handler as already run.
[1] https://review.opendev.org/708385
Change-Id: I5425a8037b6860ef71bce59becff8dfe5b601d4c
Related-Bug: #1864810
---
ansible/roles/haproxy/handlers/main.yml | 1 -
1 file changed, 1 deletion(-)
diff --git a/ansible/roles/haproxy/handlers/main.yml b/ansible/roles/haproxy/handlers/main.yml
index cec9b97acf..60fa5a03e3 100644
--- a/ansible/roles/haproxy/handlers/main.yml
+++ b/ansible/roles/haproxy/handlers/main.yml
@@ -18,7 +18,6 @@
- service.enabled | bool
notify:
- Waiting for haproxy to start
- listen: "Restart haproxy container"
- name: Restart keepalived container
vars: