-
Notifications
You must be signed in to change notification settings - Fork 2.6k
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
Changes are not reflected correctly when deleting a primary ip for a device #14532
Comments
Thank you for opening a bug report. I was unable to reproduce the reported behavior on NetBox v3.6.6. Please re-confirm the reported behavior on the current stable release and adjust your post above as necessary. Remember to provide detailed steps that someone else can follow using a clean installation of NetBox to reproduce the issue. Remember to include the steps taken to create any initial objects or other data. |
I have now tested the same on Netbox DEMO page with same behavior. I hope this gives you a better view of the issue. Preparation:
Now when deleting the IP-address we get two change logs.
|
Deployment Type
Self-hosted
NetBox Version
v3.5.7
Python Version
3.8
Steps to Reproduce
When deleting the IP-address changelog gets two entries, first one as update on device and then delete of IP-address
Expected Behavior
The device update should have following:
pre-change - original device data
post-change - the device data with null as primary_ip
Observed Behavior
The device update gets following:
pre-change - "Warning: Comparing non-atomic change to previous change record"
post-change - the device data, and it also has an IP-address id as primary_ip
Same behavior is seen in webhooks
The text was updated successfully, but these errors were encountered: