-
Radosław Piliszek authored
Since haproxy is orchestrated via site.yml in a single play, it does not need flushing handlers as handlers run will happen at the end of this play. Change-Id: Ia3743575da707325be93c39b4a2bcae9211cacb2 Related-Bug: #1864810 Closes-Bug: #1875228
Radosław Piliszek authoredSince haproxy is orchestrated via site.yml in a single play, it does not need flushing handlers as handlers run will happen at the end of this play. Change-Id: Ia3743575da707325be93c39b4a2bcae9211cacb2 Related-Bug: #1864810 Closes-Bug: #1875228
deploy.yml 308 B
---
- include_tasks: config-host.yml
- include_tasks: config.yml
# NOTE(yoctozepto): haproxy role handlers should not be flushed early.
# site.yml handles all haproxy things in a dedicated play.
# This is to avoid extra haproxy service restart.
# See: https://bugs.launchpad.net/kolla-ansible/+bug/1875228