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

Cannot add tagged VLAN from other site on multiple port edit #7581

New Issue
Closed
opened 2025-12-29 20:25:39 +01:00 by adam · 4 comments
adam commented 2025-12-29 20:25:39 +01:00
Owner
Copy Link

Originally created by @marinus81 on GitHub (Jan 30, 2023).

Originally assigned to: @dhenschen on GitHub.

NetBox version

v3.4.2

Python version

3.8

Steps to Reproduce

I have come across an issue adding VLANs to an interface if I arrive at the interfrace configuration page from the DEVICES -> Device Components -> Interfaces page, and try to edit multiple interface from the list (on the same device). I can only add VLANs as tagged VLANs if they are allocated to the same Site as the Device. This issue does not exist if I go to the Device Page and from there the Interfaces sub-page.

  1. Create Site "SITE_TEST"
  2. Create vlan 10 in Site "SITE_TEST"
  3. Create vlan 20 in no Site
  4. Create a device "DEV_TEST" in Site "SITE_TEST" with at leasttwo interfaces
  5. Navigate to DEVICES -> Device Components -> Interfaces
  6. Filter for all interfaces from device "DEV_TEST"
  7. OK: Edit single interface -> 802.1Q Switching Mode: Tagged -> Tagged VLANs includes VLAN 10 and 20 -> as expected
  8. NOK: Edit multiple interfaces -> 802.1Q Switching Mode: Tagged -> Tagged VLANs includes ony VLAN 10 -> not expected

Expected Behavior

Same behavior between "Device -> Interfaces sub-page" and "DEVICES -> Device Components -> Interfaces + filter for a device"

Observed Behavior

"Device -> Interfaces sub-page" - I can add VLANs from same site or VLANs without Site assigned
"DEVICES -> Device Components -> Interfaces + filter for a device" - I can only add VLANs from same Site as Device

Originally created by @marinus81 on GitHub (Jan 30, 2023). Originally assigned to: @dhenschen on GitHub. ### NetBox version v3.4.2 ### Python version 3.8 ### Steps to Reproduce I have come across an issue adding VLANs to an interface if I arrive at the interfrace configuration page from the DEVICES -> Device Components -> Interfaces page, and try to edit multiple interface from the list (on the same device). I can only add VLANs as tagged VLANs if they are allocated to the same Site as the Device. This issue does not exist if I go to the Device Page and from there the Interfaces sub-page. 1. Create Site "SITE_TEST" 2. Create vlan 10 in Site "SITE_TEST" 3. Create vlan 20 in no Site 4. Create a device "DEV_TEST" in Site "SITE_TEST" with at leasttwo interfaces 5. Navigate to DEVICES -> Device Components -> Interfaces 6. Filter for all interfaces from device "DEV_TEST" 7. OK: Edit single interface -> 802.1Q Switching Mode: Tagged -> Tagged VLANs includes VLAN 10 and 20 -> as expected 8. NOK: Edit multiple interfaces -> 802.1Q Switching Mode: Tagged -> Tagged VLANs includes ony VLAN 10 -> not expected ### Expected Behavior Same behavior between "Device -> Interfaces sub-page" and "DEVICES -> Device Components -> Interfaces + filter for a device" ### Observed Behavior "Device -> Interfaces sub-page" - I can add VLANs from same site or VLANs without Site assigned "DEVICES -> Device Components -> Interfaces + filter for a device" - I can only add VLANs from same Site as Device
adam added the type: bugstatus: accepted labels 2025-12-29 20:25:39 +01:00
adam closed this issue 2025-12-29 20:25:40 +01:00
adam commented 2025-12-29 20:25:40 +01:00
Author
Owner
Copy Link

@HolySephi commented on GitHub (Jan 31, 2023):

This bug is also present in editing a prefix. Only site specific VLANs are shown - not site-less VLANs.
I guess because the site field for the prefix is also a filter for the VLAN field.
If should always list site-specific VLANs and site-less VLANs (for example if you want prefixes to be assigned to a site but not VLANs)

@HolySephi commented on GitHub (Jan 31, 2023): This bug is also present in editing a prefix. Only site specific VLANs are shown - not site-less VLANs. I guess because the site field for the prefix is also a filter for the VLAN field. If should always list site-specific VLANs and site-less VLANs (for example if you want prefixes to be assigned to a site but not VLANs)
adam commented 2025-12-29 20:25:41 +01:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (May 2, 2023):

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. NetBox is governed by a small group of core maintainers which means not all opened issues may receive direct feedback. Do not attempt to circumvent this process by "bumping" the issue; doing so will result in its immediate closure and you may be barred from participating in any future discussions. Please see our contributing guide.

@github-actions[bot] commented on GitHub (May 2, 2023): This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. NetBox is governed by a small group of core maintainers which means not all opened issues may receive direct feedback. **Do not** attempt to circumvent this process by "bumping" the issue; doing so will result in its immediate closure and you may be barred from participating in any future discussions. Please see our [contributing guide](https://github.com/netbox-community/netbox/blob/develop/CONTRIBUTING.md).
adam commented 2025-12-29 20:25:41 +01:00
Author
Owner
Copy Link

@dhenschen commented on GitHub (May 8, 2023):

I'm interested in taking ownership of this issue.

I've ran into this before while using NetBox and would like to see it fixed.

@dhenschen commented on GitHub (May 8, 2023): I'm interested in taking ownership of this issue. I've ran into this before while using NetBox and would like to see it fixed.
adam commented 2025-12-29 20:25:41 +01:00
Author
Owner
Copy Link

@dhenschen commented on GitHub (May 16, 2023):

I opened https://github.com/netbox-community/netbox/issues/12622 to track a related bug that impacts the creation and import of prefixes in IPAM. The fix for that issue is different than what will be required for this issue.

@dhenschen commented on GitHub (May 16, 2023): I opened https://github.com/netbox-community/netbox/issues/12622 to track a related bug that impacts the creation and import of prefixes in IPAM. The fix for that issue is different than what will be required for this issue.
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#7581
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?