designate_backend_bind9 container restarting

[Eric Miller]

This only happens on Kolla-Ansible 7.0.0.0b3, not 6.1.0. Both built with source option very recently.
Distro: CentOS 7.5

Fresh deploy with quite a few components installed, the designate_backend_bind9 container restarts itself continuously. The other Designate containers are fine.

The "docker logs" show:

14-Aug-2018 23:56:38.497 ----------------------------------------------------
14-Aug-2018 23:56:38.497 BIND 9 is maintained by Internet Systems Consortium,
14-Aug-2018 23:56:38.497 Inc. (ISC), a non-profit 501(c)(3) public-benefit
14-Aug-2018 23:56:38.497 corporation. Support and training for BIND 9 are
14-Aug-2018 23:56:38.497 available at https://www.isc.org/support
14-Aug-2018 23:56:38.497 ----------------------------------------------------
14-Aug-2018 23:56:38.497 found 6 CPUs, using 6 worker threads
14-Aug-2018 23:56:38.497 using 6 UDP listeners per interface
14-Aug-2018 23:56:38.498 using up to 21000 sockets
14-Aug-2018 23:56:38.515 loading configuration from '/etc/named.conf'
14-Aug-2018 23:56:38.515 /etc/named.conf:10: expected IP address near ';'
14-Aug-2018 23:56:38.517 loading configuration: unexpected token
14-Aug-2018 23:56:38.517 exiting (due to fatal error)

Eric

[Eduardo Gonzalez (egonzalez90)]

Hi, can you show your named.conf at /etc/kolla/designate-backend-bind/ ?

[Eduardo Gonzalez (egonzalez90)]

Is a bug introduced by https://github.com/openstack/kolla-ansible/commit/4157f30c5f936ad8d8ba38e41321fbbae17a7d60

An if is missing for the forwarders variable

[Eric Miller (erickmiller)]

Contents of the named.conf file are:

include "/etc/rndc.key";
options {
        listen-on port 53 { 192.168.1.3; };
        directory "/var/lib/named";
        allow-new-zones yes;
        dnssec-validation yes;
        auth-nxdomain no;
        request-ixfr no;
        recursion no;
        forwarders { ; };
        minimal-responses yes;
        allow-notify { 192.168.1.1;192.168.1.2;192.168.1.3; };
};

controls {
        inet 192.168.1.3 port 953 allow { 192.168.1.1; 192.168.1.2; 192.168.1.3; } keys { "rndc-key"; };
};

[Eric Miller (erickmiller)]

I just checked a 6.1.0 install and its named.conf file contains:

include "/etc/rndc.key";
options {
        listen-on port 53 { 192.168.1.1; };
        directory "/var/lib/named";
        allow-new-zones yes;
        dnssec-validation auto;
        auth-nxdomain no;
        request-ixfr no;
        recursion no;
        minimal-responses yes;
        allow-notify { 192.168.1.1;192.168.1.2;192.168.1.3; };
};

controls {
        inet 192.168.1.1 port 953 allow { 192.168.1.1; 192.168.1.2; 192.168.1.3; } keys { "rndc-key"; };
};

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.openstack.org/591912

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/591912
Committed: https://git.openstack.org/cgit/openstack/kolla-ansible/commit/?id=fae046ece81b5fb1d4fce635fc97574eeb8693ab
Submitter: Zuul
Branch: master

commit fae046ece81b5fb1d4fce635fc97574eeb8693ab
Author: Eduardo Gonzalez <email address hidden>
Date: Wed Aug 15 08:24:48 2018 +0200

    Fixes bind9 restarting when no designate_forwarders_addresses

    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

[OpenStack Infra (hudson-openstack)]

This issue was fixed in the openstack/kolla-ansible 7.0.0.0rc1 release candidate.