designate_backend_bind refuses notifications

Bug #1773972 reported by Vladislav Belogrudov
12
This bug affects 1 person
Affects Status Importance Assigned to Milestone
kolla-ansible
Incomplete
Undecided
Gaël THEROND

Bug Description

after following kolla designate deployment guide recordsets are created but fail after a few minutes. Bind containers report:

29-May-2018 12:36:01.040 client 10.196.245.201#34436: received notify for zone 'sample.mysuperopenstack.org'
29-May-2018 12:36:01.041 zone sample.mysuperopenstack.org/IN: refused notify from non-master: 10.196.245.201#34436
29-May-2018 12:36:01.337 client 10.196.245.202#58067: received notify for zone 'sample.mysuperopenstack.org'
29-May-2018 12:36:01.337 zone sample.mysuperopenstack.org/IN: refused notify from non-master: 10.196.245.202#58067

Only when I manually restart designate_backend_bind9 containers on all hosts all following records are successfully created and bind does not object

Revision history for this message
Vladislav Belogrudov (vlad-belogrudov) wrote :

sample named.conf:

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

controls {
        inet 10.196.245.203 port 953 allow { 10.196.245.201; 10.196.245.202; 10.196.245.203; } keys { "rndc-key"; };
};

All bind9 containers have the same configuration on hosts and inside theirs /etc/

Revision history for this message
Vladislav Belogrudov (vlad-belogrudov) wrote :

dig +multi @10.196.245.203 sample.mysuperopenstack.org. soa
dig +multi @10.196.245.201 sample.mysuperopenstack.org. soa
differ in serial.

on non-restarted named shows different serial compared to restarted containers.

Revision history for this message
Gaël THEROND (gtherond) wrote :

Looks like a pool setting issue.
Could you post your ns_records value and the output of designate-manage pool show_config ?

Gaël THEROND (gtherond)
Changed in kolla-ansible:
assignee: nobody → Gaël THEROND (fl1nt)
status: New → Confirmed
Changed in kolla-ansible:
status: Confirmed → In Progress
Revision history for this message
Dr. Jens Harbott (j-harbott) wrote :

Without the information about how the pool configuration looks like, it is not possible to handle this bug.

Changed in kolla-ansible:
status: In Progress → Incomplete
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Change abandoned on kolla-ansible (master)

Change abandoned by "Gaël THEROND <email address hidden>" on branch: master
Review: https://review.opendev.org/c/openstack/kolla-ansible/+/878270
Reason: I'm fed up with those back and forth nonsense.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.