c5f9ea9590
It turned out the previous fix ([1]) was incomplete.
Additionally, it seems we have to limit Tacker server
to one instance co-located with conductor.
[1] https://review.opendev.org/684275
commit b96ade3cf0
Change-Id: I9ce27d5f68f32ef59e245960e23336ae5c5db905
Closes-bug: #1853715
Related-bug: #1845142
39 lines
1.1 KiB
YAML
39 lines
1.1 KiB
YAML
---
|
|
- name: Warn about Train upgrade
|
|
debug:
|
|
msg: >-
|
|
In Train, Tacker started using local filesystem to store VNF
|
|
packages and CSAR files.
|
|
Kolla Ansible provides no shared filesystem capabilities, hence only
|
|
one instance of each Tacker service is deployed and all on the same host.
|
|
Previous multinode deployments will be descaled when running upgrade.
|
|
|
|
- name: Stop and remove extra tacker-conductor containers
|
|
vars:
|
|
service_name: "tacker-conductor"
|
|
service: "{{ tacker_services[service_name] }}"
|
|
become: true
|
|
kolla_docker:
|
|
action: "stop_and_remove_container"
|
|
name: "{{ service.container_name }}"
|
|
when:
|
|
- inventory_hostname not in tacker_hosts
|
|
|
|
- name: Stop and remove extra tacker-server containers
|
|
vars:
|
|
service_name: "tacker-server"
|
|
service: "{{ tacker_services[service_name] }}"
|
|
become: true
|
|
kolla_docker:
|
|
action: "stop_and_remove_container"
|
|
name: "{{ service.container_name }}"
|
|
when:
|
|
- inventory_hostname not in tacker_hosts
|
|
|
|
- include_tasks: config.yml
|
|
|
|
- include_tasks: bootstrap_service.yml
|
|
|
|
- name: Flush handlers
|
|
meta: flush_handlers
|