Bug 2220930
| Summary: | Designate DNS - enabling "DesignateBindQueryLogging" is not followed by designate_backend_bind9 restart | ||
|---|---|---|---|
| Product: | Red Hat OpenStack | Reporter: | Arkady Shtempler <ashtempl> |
| Component: | tripleo-ansible | Assignee: | Brent Eagles <beagles> |
| Status: | CLOSED ERRATA | QA Contact: | Lilach Avraham <lavraham> |
| Severity: | high | Docs Contact: | |
| Priority: | high | ||
| Version: | 17.1 (Wallaby) | CC: | beagles, gbrinn, gregraka, joflynn, lavraham, mariel, scohen |
| Target Milestone: | z2 | Keywords: | Triaged |
| Target Release: | 17.1 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | tripleo-ansible-3.3.1-17.1.20231101230823.4d015bf.el9ost | Doc Type: | Bug Fix |
| Doc Text: |
Before this update, in environments that ran the DNS service (designate), there was a known issue where the `bind9` and `unbound` services did not automatically restart if the configuration changed. With this update, the `bind9` and `unbound` services automatically restart if the configuration changes.
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2024-01-16 14:32:51 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
I did the configuration functionality parts, I got the query messages that we expected: ==> designate-bind-query.log <== 22-Nov-2023 10:48:20.074 queries: info: client @0x7ffbcc088d08 10.0.0.48#35156 (support.example.com): query: support.example.com IN A +E(0)K (10.0.0.148) I move this BZ to VERIFIED. 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 (Red Hat OpenStack Platform 17.1.2 bug fix and enhancement advisory), 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/RHBA-2024:0209 |
Scenario: ### Configuration part ### Enable DesignateBindQueryLogging 1) Create logging.yaml with: parameter_defaults: DesignateBindQueryLogging: True 2) Add logging.yaml into the overcloud_deploy.sh script ... -e /home/stack/logging.yaml \ ... 3) Update OC with: . stackrc ./overcloud_deploy.sh Make sure 1) OC is successfully deployed 2) SSH To Controller and make sure you see:querylog True; in /var/lib/config-data/ansible-generated/designate/etc/named/options.conf ### Functionality part ### Create a zone: openstack zone create --email stam example2.com. Create A type recordset for previously created zone with: openstack recordset create example2.com. --type A --record 192.0.2.21 --ttl 1000 --description example2_recordset_a support From your Undercloud host connect to all Controllers and detect the BIND9 IP using: sudo netstat -antp | grep ":53" | grep named Note: the above command is used to detect TCP only BIND. (-t) Monitor Bind's logs whilr digging Bind SSH to one of the Controllers and start: cd /var/log/containers/designate-bind tail -f * From the Undercloud host execute: dig @10.0.0.108 -p 53 +noall +answer +multiline example2.com. NS +short dig @10.0.0.108 -p 53 +noall +answer +multiline example2.com. SOA +short dig @10.0.0.108 -p 53 +noall +answer +multiline support.example2.com. A +short Expected result: You should see quary messages like this one: "24-Mar-2022 15:52:00.178 queries: info: client @0x7f34380446a0 10.155.105.100#54387 (www.akamai.com): query: www.akamai.com IN A +" logged.