Skip to content

DCIM Interface: ObjectChange missing for deleted untagged VLANs #18717

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.

Sign up for GitHub

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

Jump to bottom
Closed
moonrail opened this issue Feb 24, 2025 · 0 comments · Fixed by #19308
Closed

DCIM Interface: ObjectChange missing for deleted untagged VLANs #18717

moonrail opened this issue Feb 24, 2025 · 0 comments · Fixed by #19308
Assignees
@bctiemann
Labels
severity: low Does not significantly disrupt application functionality, or a workaround is available status: accepted This issue has been accepted for implementation type: bug A confirmed report of unexpected behavior in the application
Milestone
v4.2.9

Comments

@moonrail
Copy link

moonrail commented Feb 24, 2025 •
edited
Loading

Deployment Type

NetBox Cloud (demo), Self-hosted

NetBox Version

v4.2.0 (demo.netbox.dev) & v4.1.11 (locally)

Python Version

3.11

Steps to Reproduce

  1. Have an Device with an Interface
  2. Have two VLANs: A & B
  3. Set Device Interface mode to "tagged"
  4. Add VLAN A as untagged VLAN to Interface
  5. Add VLAN B as tagged VLAN to Interface
  6. Delete VLAN B
  7. Delete VLAN A

Expected Behavior

Interface ObjectChange update for each VLAN deletion:

  1. tagged_vlans to empty list
  2. untagged_vlan to null/None

Observed Behavior

Only one Interface ObjectChange update is created for VLAN deletion: tagged_vlans.

No Interface ObjectChange is created for untagged_vlan when related VLAN is deleted. According to Interface Changelog the Interface still has an untagged_vlan when in fact it does not exist anymore.
@moonrail moonrail added status: needs triage This issue is awaiting triage by a maintainer type: bug A confirmed report of unexpected behavior in the application labels Feb 24, 2025
@bctiemann bctiemann added status: needs owner This issue is tentatively accepted pending a volunteer committed to its implementation severity: low Does not significantly disrupt application functionality, or a workaround is available and removed status: needs triage This issue is awaiting triage by a maintainer labels Feb 24, 2025
@bctiemann bctiemann self-assigned this Apr 24, 2025
@bctiemann bctiemann added status: accepted This issue has been accepted for implementation and removed status: needs owner This issue is tentatively accepted pending a volunteer committed to its implementation labels Apr 24, 2025
@bctiemann bctiemann mentioned this issue Apr 24, 2025
Merged
@jnovinger jnovinger added this to the v4.2.9 milestone Apr 24, 2025
@jeremystretch jeremystretch mentioned this issue Apr 30, 2025
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@bctiemann bctiemann

Labels
severity: low Does not significantly disrupt application functionality, or a workaround is available status: accepted This issue has been accepted for implementation type: bug A confirmed report of unexpected behavior in the application
Projects
None yet
Milestone
v4.2.9
3 participants
@jnovinger @bctiemann @moonrail