starred/netbox
1
0
Fork 0
mirror of https://github.com/netbox-community/netbox.git synced 2026-01-11 21:10:29 +01:00
Code Issues 273 Packages Projects Releases 10 Wiki Activity

VLAN Members shows same interface multiple times #2190

New Issue
Closed
opened 2025-12-29 17:23:09 +01:00 by adam · 3 comments
adam commented 2025-12-29 17:23:09 +01:00
Owner
Copy Link

Originally created by @Limb on GitHub (Dec 11, 2018).

Environment

  • Python version: 3.6.7
  • NetBox version: 2.5.0

Steps to Reproduce

  1. Create a device with (3) interfaces gi-[0-2]
  2. Create (3) VLAN's [id 1,2,3]
  3. Set gi-0 802.1Q Mode to Tagged and add VLAN 1 as untagged, VLAN2 and 3 as tagged.
  4. Set gi-1 802.1Q Mode to Tagged and add VLAN 1 as untagged, VLAN 2 as tagged.
  5. Set gi-2 802.1Q Mode to Access and add VLAN 1 as untagged.
  6. View VLAN 1 Members

Expected Behavior

The members table for VLAN 1 should list interface gi-0, gi-1 and gi-2 as members of the VLAN.

Observed Behavior

Interface gi-0 is listed twice, follow by gi-1. If the table is sorted in reverse (sort=-name) the three individual entries appear.

Originally created by @Limb on GitHub (Dec 11, 2018). <!-- NOTE: This form is only for reproducible bugs. If you need assistance with NetBox installation, or if you have a general question, DO NOT open an issue. Instead, post to our mailing list: https://groups.google.com/forum/#!forum/netbox-discuss Please describe the environment in which you are running NetBox. Be sure that you are running an unmodified instance of the latest stable release before submitting a bug report. --> ### Environment * Python version: 3.6.7 * NetBox version: 2.5.0 <!-- Describe in detail the steps that someone else can take to reproduce this bug using the current stable release of NetBox (or the current beta release where applicable). --> ### Steps to Reproduce 1. Create a device with (3) interfaces gi-[0-2] 2. Create (3) VLAN's [id 1,2,3] 3. Set gi-0 802.1Q Mode to Tagged and add VLAN 1 as untagged, VLAN2 and 3 as tagged. 4. Set gi-1 802.1Q Mode to Tagged and add VLAN 1 as untagged, VLAN 2 as tagged. 5. Set gi-2 802.1Q Mode to Access and add VLAN 1 as untagged. 6. View VLAN 1 Members <!-- What did you expect to happen? --> ### Expected Behavior The members table for VLAN 1 should list interface gi-0, gi-1 and gi-2 as members of the VLAN. <!-- What happened instead? --> ### Observed Behavior Interface gi-0 is listed twice, follow by gi-1. If the table is sorted in reverse (sort=-name) the three individual entries appear.
adam added the type: bugstatus: accepted labels 2025-12-29 17:23:09 +01:00
adam closed this issue 2025-12-29 17:23:09 +01:00
adam commented 2025-12-29 17:23:10 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Dec 11, 2018):

Create VLAN (id 1000 in this case)and then assign multiple different interfaces from a device to that VLAN.

Please revise your issue to include the exact steps that can be taken to reproduce this issue.

@jeremystretch commented on GitHub (Dec 11, 2018): > Create VLAN (id 1000 in this case)and then assign multiple different interfaces from a device to that VLAN. Please revise your issue to include the exact steps that can be taken to reproduce this issue.
adam commented 2025-12-29 17:23:10 +01:00
Author
Owner
Copy Link

@Limb commented on GitHub (Dec 12, 2018):

I have figured out the way to reproduce this issue and updated the original comment.

In addition I'll add that on my production instance with more interfaces in the VLAN the same interface is repeated for 4 out of the 5 VLAN members.

@Limb commented on GitHub (Dec 12, 2018): I have figured out the way to reproduce this issue and updated the original comment. In addition I'll add that on my production instance with more interfaces in the VLAN the same interface is repeated for 4 out of the 5 VLAN members.
adam commented 2025-12-29 17:23:11 +01:00
Author
Owner
Copy Link

@DanSheps commented on GitHub (Dec 12, 2018):

I checked our production netbox and I am not seeing this issue on our production. Do you have duplicate interfaces?

Just saw the edited post

@DanSheps commented on GitHub (Dec 12, 2018): ~~I checked our production netbox and I am not seeing this issue on our production. Do you have duplicate interfaces?~~ Just saw the edited post
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
beta
breaking change
complexity: high
complexity: low
complexity: medium
needs milestone
netbox
pending closure
plugin candidate
pull-request
Mirrored from GitHub Pull Request
 severity: high
severity: low
severity: medium
status: accepted
status: backlog
status: blocked
status: duplicate
status: needs owner
status: needs triage
status: revisions needed
status: under review
topic: GraphQL
topic: Internationalization
topic: OpenAPI
topic: UI/UX
topic: cabling
topic: event rules
topic: htmx navigation
topic: industrialization
topic: migrations
topic: plugins
topic: scripts
topic: templating
topic: testing
type: bug
type: deprecation
type: documentation
type: feature
type: housekeeping
type: translation
No Label status: accepted type: bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
adam
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/netbox#2190
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?