designate: bind server refuse notify from worker

[Kevin Tibi]

On fresh deploy, If I create a new records in zone, bind serveur refuse the notify from worker :

26-Jan-2018 14:49:07.202 received control channel command 'addzone test.toto { type slave; masters { 172.16.5.2 port 5354; 172.16.5.3 port 5354; 172.16.5.4 port 5354;}; file "slave.test.toto.ba226b33-94fb-4267-8408-d42a70c1f675"; };'
26-Jan-2018 14:49:07.202 zone test.toto added to view _default via addzone
26-Jan-2018 14:49:07.235 client 172.16.7.3#56210: received notify for zone 'test.toto'
26-Jan-2018 14:49:07.235 zone test.toto/IN: refused notify from non-master: 172.16.7.3#56210
26-Jan-2018 14:49:07.355 zone test.toto/IN: Transfer started.
26-Jan-2018 14:49:07.355 transfer of 'test.toto/IN' from 172.16.5.2#5354: connected using 172.16.5.2#54748
26-Jan-2018 14:49:07.496 zone test.toto/IN: transferred serial 1516974546
26-Jan-2018 14:49:07.496 transfer of 'test.toto/IN' from 172.16.5.2#5354: Transfer completed: 1 messages, 3 records, 138 bytes, 0.140 secs (985 bytes/sec)
26-Jan-2018 14:53:47.065 client 172.16.7.3#38346: received notify for zone 'test.toto'
26-Jan-2018 14:53:47.065 zone test.toto/IN: refused notify from non-master: 172.16.7.3#38346
26-Jan-2018 15:09:22.440 received control channel command 'delzone test.toto '
26-Jan-2018 15:09:22.440 zone test.toto removed via delzone

We can see the creation of the zone work because worker use control channel (port 953 with rdnc). But records creation use notify (port 53). In this bug https://bugs.launchpad.net/kolla-ansible/+bug/1740455, the workaround is to disable notify on worker. So maybe you can force to use RDNC for add records.

Without that, I need to add special option in bind for allow notify from worker.

e.g : juju use that for notify https://github.com/openstack/charm-designate-bind/blob/master/src/templates/named.conf.options#L29

[OpenStack Infra (hudson-openstack)]

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

commit 7892826743141fb881e05d3a4aca7b0e7f3f12e7
Author: Kevin TIBI <email address hidden>
Date: Mon Jan 29 10:44:29 2018 +0100

    Add permission to notify dns server from worker

    Change-Id: I67ea2b1a91dfd61341ae2e5bcd82d1cf0597fe9c
    Closes-Bug: #1745957

[OpenStack Infra (hudson-openstack)]

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

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: stable/pike
Review: https://review.openstack.org/550420

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/550420
Committed: https://git.openstack.org/cgit/openstack/kolla-ansible/commit/?id=a655df733ee2b9438bf38791cb9ff3dfcfcadfb6
Submitter: Zuul
Branch: stable/pike

commit a655df733ee2b9438bf38791cb9ff3dfcfcadfb6
Author: Kevin TIBI <email address hidden>
Date: Mon Jan 29 10:44:29 2018 +0100

    Add permission to notify dns server from worker

    Change-Id: I67ea2b1a91dfd61341ae2e5bcd82d1cf0597fe9c
    Closes-Bug: #1745957
    (cherry picked from commit 7892826743141fb881e05d3a4aca7b0e7f3f12e7)

[OpenStack Infra (hudson-openstack)]

This issue was fixed in the openstack/kolla-ansible 5.0.3 release.