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.
Reviewed: https:/ /review. opendev. org/723878 /git.openstack. org/cgit/ openstack/ kolla-ansible/ commit/ ?id=72cd552d794 a77666387749cc9 4e5a4f50661d47
Committed: https:/
Submitter: Zuul
Branch: stable/stein
commit 72cd552d794a776 66387749cc94e5a 4f50661d47
Author: Radosław Piliszek <email address hidden>
Date: Sun Apr 26 19:59:26 2020 +0200
Remove redundant listen on haproxy handler
Follow-up on [1] "Avoid multiple haproxy restarts after tion".
reconfigura
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: I5425a8037b6860 ef71bce59becff8 dfe5b601d4c c5a7dfaca6c3665 27f584afc0)
Related-Bug: #1864810
(cherry picked from commit 98e86ea62b64eb1