openstack/kolla-ansible
Code Issues Proposed changes

Make no_proxy handling more robust

Browse Source 
This fixes an issue with Bifrost that setting
kolla_internal_vip_address became mandatory.

Additionally, it does a better job ensuring the syntax is
correct when any of the entries is missing.

Change-Id: Ie86a345365ca3766aebd8a29ce329b370e61af6c
Closes-Bug: #1894199
This commit is contained in:
Radosław Piliszek 2020-09-04 11:13:52 +02:00
parent 58e886b370
commit 2a4fb438fe
1 changed files with 6 additions and 1 deletions

7
ansible/group_vars/all.yml

@ -57,10 +57,15 @@ container_http_proxy: ""
container_https_proxy: ""
container_no_proxy: "localhost,127.0.0.1"
container_proxy_no_proxy_entries:
- "{{ container_no_proxy }}"
- "{{ api_interface_address }}"
- "{{ kolla_internal_vip_address | default('') }}"
container_proxy:
http_proxy: "{{ container_http_proxy }}"
https_proxy: "{{ container_https_proxy }}"
no_proxy: "{{ container_no_proxy }},{{ api_interface_address }},{{ kolla_internal_vip_address }}"
no_proxy: "{{ container_proxy_no_proxy_entries | select | join(',') }}"
# By default, Kolla API services bind to the network address assigned
# to the api_interface. Allow the bind address to be an override.