DNS Integration throws expection logs entries were warnings would be sufficient
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
neutron |
Fix Released
|
Medium
|
Jayce Houtman |
Bug Description
The DNS Integration in the ML2 drivers generates exception LOG entries whenever dns_exc.
The exceptions serve to alert the administrators that there was an issue with the record set's creation. However, I believe a warning would be sufficiently informative for the administrators to recognize that something did not proceed as anticipated, which would prevent stack traces in the logs. An error could also serve this purpose, but I think a warning is more suitable since the system remains operational when the exceptions are caught within Neutron.
Example stack trace of a duplicate record set: https:/
The stack traces comes from our deployment which runs version 2023.1 deployed with Kolla-Ansible. We use OpenStack Designate as our DNS driver.
I have already submitted a review to modify the exceptions to warnings, which also eliminates the catching of dns_exc.
Changed in neutron: | |
status: | New → In Progress |
Changed in neutron: | |
assignee: | nobody → Jayce Houtman (houtknots) |
Changed in neutron: | |
importance: | Undecided → Medium |
tags: | added: dns |
Reviewed: https:/ /review. opendev. org/c/openstack /neutron/ +/900212 /opendev. org/openstack/ neutron/ commit/ 5fe5188ce513c92 8b45cbc890bed80 d8d5a2106b
Committed: https:/
Submitter: "Zuul (22348)"
Branch: master
commit 5fe5188ce513c92 8b45cbc890bed80 d8d5a2106b
Author: Jayce Houtman <email address hidden>
Date: Mon Nov 6 17:23:44 2023 +0100
Change exception messages to error log messages for DNS integration.
Change non-harmful stack trace errors for dns_exc. DNSDomainNotFou nd and exc.DuplicateRe cordSet to error log messages. This prevents the logs
dns_
from filling with stack traces where error messages would have been
sufficient enough.
Closes-Bug: #2042925 506392f16c579de 6d92cd56c23
Change-Id: Icf1fff28bb560c