openstack/kolla-ansible
Code Issues Proposed changes

Fixes bind9 restarting when no designate_forwarders_addresses

Browse Source 
When deploying designate if no designate_forwarders_addresses
is provided, bind9 container keeps restarting due an invalid(empty)
forwarder addresses is set in named.conf

Change-Id: I7d309eb077243435dd2038629074251abec7d3e1
Closes-Bug: #1787092
This commit is contained in:
Eduardo Gonzalez 2018-08-15 08:24:48 +02:00
parent 0a2ce9a93c
commit fae046ece8
1 changed files with 3 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

3
ansible/roles/designate/templates/named.conf.j2
View File

@ -1,3 +1,4 @@
#jinja2: trim_blocks: False
include "/etc/rndc.key";
options {
listen-on port {{ designate_bind_port }} { {{ hostvars[inventory_hostname]['ansible_' + hostvars[inventory_hostname]['api_interface']]['ipv4']['address'] }}; };
@ -7,7 +8,9 @@ options {
auth-nxdomain no;
request-ixfr no;
recursion {{ designate_recursion }};
{% if designate_forwarders_addresses %}
forwarders { {{ designate_forwarders_addresses }}; };
{% endif %}
minimal-responses yes;
allow-notify { {% for host in groups['designate-worker'] %}{{ hostvars[host]['ansible_' + hostvars[host]['api_interface']]['ipv4']['address'] }};{% endfor %} };
};