Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

When an address record is updated, the PTR record for it is saved even if if didn't change #278

Closed
peteeckel opened this issue Jun 2, 2024 · 0 comments · Fixed by #279
Closed
Assignees
Labels
bug Something isn't working

Comments

@peteeckel
Copy link
Owner

Versions
NetBox Version: 4.0.2
NetBox DNS Version: 1.0.1
Python Version: 3.11.5

Describe the bug
When writing the tests for the #89, I found that some changes to address records were handled inefficienty, leading to the redunsant invocation of event rules.

To Reproduce
Steps to reproduce the behavior:

  1. Create an event rule and a webhook for Record | update
  2. Create a forward and a reverse zone
  3. Create an address record that has a PTR record in the reverse zone
  4. Verify both records are present
  5. Now add tags to the address record without changing anything else and watch for event rule invocations

Expected result
One event rule is triggered for the address record, and none for the PTR record

Actual result
One event rule is triggered for both.

What's causing this is that the PTR record is saved whenever its address record is saved, even if nothing at all changed in its values.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant