04effaa903
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
23 lines
803 B
YAML
23 lines
803 B
YAML
---
|
|
- include_tasks: config-host.yml
|
|
|
|
- include_tasks: config.yml
|
|
|
|
- name: Stopping all slave keepalived containers
|
|
vars:
|
|
key: "{{ 'ipv6' if api_address_family == 'ipv6' else 'ipv4_secondaries' }}"
|
|
addresses: "{{ hostvars[inventory_hostname]['ansible_' + api_interface].get(key, []) | map(attribute='address') | list }}"
|
|
become: true
|
|
kolla_docker:
|
|
action: "stop_container"
|
|
common_options: "{{ docker_common_options }}"
|
|
name: "keepalived"
|
|
when: kolla_internal_vip_address not in addresses
|
|
notify:
|
|
- Restart keepalived container
|
|
|
|
# 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
|