During tempest testing we are seeing the following messages in the designate-bind log file: designate-bind.log:25-Jul-2022 23:51:48.920 notify: info: client @0x7f5338001dc8 10.0.0.106#44545: received notify for zone '24.168.192.in-addr.arpa' designate-bind.log:25-Jul-2022 23:51:48.920 general: info: zone 24.168.192.in-addr.arpa/IN: refused notify from non-master: 10.0.0.106#44545 In this deployment the controllers are: controller-0.external 10.0.0.142 controller-1.external 10.0.0.106 controller-2.external 10.0.0.108 The bind9/named configuration file /etc/named/options.conf has: listen-on port 53 { 10.0.0.109; }; allow-notify { 10.0.0.109; }; ip a for the container: 7: br-ex: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UNKNOWN group default qlen 1000 link/ether 52:54:00:14:39:93 brd ff:ff:ff:ff:ff:ff inet 10.0.0.142/24 brd 10.0.0.255 scope global br-ex valid_lft forever preferred_lft forever inet 10.0.0.109/32 scope global br-ex valid_lft forever preferred_lft forever inet6 fe80::5054:ff:fe14:3993/64 scope link valid_lft forever preferred_lft forever We need to add/append the controller external IPs to this allow-notify list.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (Release of components for Red Hat OpenStack Platform 17.0 (Wallaby)), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHEA-2022:6543