Strange behaviour with generated >3 VLANs table for interfaces #17771
Labels
severity: low
Does not significantly disrupt application functionality, or a workaround is available
status: needs owner
This issue is tentatively accepted pending a volunteer committed to its implementation
type: bug
A confirmed report of unexpected behavior in the application
Comments
Azmodeszer
added
status: needs triage
arthanson
added
status: needs owner
|
I can confirm that we see the same behaviour. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Deployment Type
Self-hosted
Triage priority
N/A
NetBox Version
v4.1.4
Python Version
3.11
Steps to Reproduce
I'm seeing some weird behaviour with the new feature as implemented per #17655. I can't give exact guaranteed reproduction steps, because it might be something specific to my database that I haven't figured out yet, but basically:
/ipam/vlans/?interface_id=<ID>).Expected Behavior
Tagged VLANs for that interface are shown correctly.
Observed Behavior
What I am seeing is some of the tagged VLANs being listed multiple times (and the untagged VLAN showing up as well, which I guess is to be expected). I've tried to reproduce it with new VLANs created after the update to 4.1.4 and it seems to work as expected with those (some "older" VLANs are also only showing up once, however, so it might not be related to that at all), but when I attach a certain existing VLAN as tagged to the interface it results in multiple redundant rows again.
The text was updated successfully, but these errors were encountered: