yahoo-eng-team team mailing list archive

[Jayce Houtman <2042925@xxxxxxxxxxxxxxxxxx>]

Public bug reported:


The DNS Integration in the ML2 drivers generates exception LOG entries whenever dns_exc.DNSDomainNotFound and dns_exc.DuplicateRecordSet are triggered on the creation or deletion of DNS records. These exceptions occur if a duplicate record set is found or if the DNS domain is not located.

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://jhcsmedia.com/?f=stack_trace_neutron_900212.txt
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.DuplicateRecordSet when
removing DNS records. This change is based on the premise that duplicate
record sets should not exist initially.
https://review.opendev.org/c/openstack/neutron/+/900212

** Affects: neutron
     Importance: Undecided
         Status: In Progress

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/2042925

Title:
  DNS Integration throws expection logs entries were warnings would be
  sufficient

Status in neutron:
  In Progress

Bug description:
  
  The DNS Integration in the ML2 drivers generates exception LOG entries whenever dns_exc.DNSDomainNotFound and dns_exc.DuplicateRecordSet are triggered on the creation or deletion of DNS records. These exceptions occur if a duplicate record set is found or if the DNS domain is not located.

  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://jhcsmedia.com/?f=stack_trace_neutron_900212.txt
  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.DuplicateRecordSet when removing DNS records. This change is
  based on the premise that duplicate record sets should not exist
  initially. https://review.opendev.org/c/openstack/neutron/+/900212

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/2042925/+subscriptions