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

Unable to select VLANs on Device Interfaces where they are scoped by Cluster or Cluster Groups #11070

New Issue
Open
opened 2025-12-29 21:39:50 +01:00 by adam · 4 comments
adam commented 2025-12-29 21:39:50 +01:00
Owner
Copy Link

Originally created by @SteveRodrigue on GitHub (Apr 22, 2025).

NetBox version

v4.2.4

Feature type

Change to existing functionality

Proposed functionality

It was suggested in issue #12764 to make it a formal feature request. This was also reported in issue #12690.

Assigning VLANs from a VLAN groups should work in all context in the Netbox UI. At the moment, when using the API or Netbox Scripts we can properly assign VLAN(s) to interface(s) based on specific VLAN Groups, but we can't from dcim/interfaces/.

Here's the workflow:

  1. Create a device.
  2. Assign the device to a virtualization cluster.
  3. Create a VLAN group attached to the cluster.
  4. Create VLAN(s) in the VLAN group.
  5. Can't assign VLAN(s) from the VLAN group on the device interfaces manually in the GUI.
  6. Can assign VLAN(s) using the API or a Netbox Scripts.

When we modify an interface and want to assign a VLAN based on a VLAN group, the "dropdown menu/list" of Untagged VLAN and Tagged VLANs is empty even if VLANs exist in the selected VLAN group.

Image

Use case

We are allowed to create VLANs and VLAN groups, we should be able to assign any of those VLANs in the Netbox Web UI.

Creating VLAN groups is common in virtualization or when we group devices that shares VLANs: VTP domain (people still uses those), any Network Fabric or cluster of devices (or servers).

Database changes

I don't think any database change is required, the API already allows proper assignment of VLANs that are member of a group. This is actually how we work around the issue at the moment: we have created a form with a Netbox Scripts that allows us to add/remove VLANs to an interface manually. We override the UI limitation.

I feel the current limitation, is mainly due to the Web UI vlan lookup logic: when selecting a VLAN group, the list/dropdown is empty (the query may need to be fine tuned).

External dependencies

N/A

Originally created by @SteveRodrigue on GitHub (Apr 22, 2025). ### NetBox version v4.2.4 ### Feature type Change to existing functionality ### Proposed functionality It was suggested in [issue #12764](https://github.com/netbox-community/netbox/issues/12764) to make it a formal feature request. This was also reported in [issue #12690](https://github.com/netbox-community/netbox/issues/12690). Assigning VLANs from a VLAN groups should work in all context in the Netbox UI. At the moment, when using the API or Netbox Scripts we can properly assign VLAN(s) to interface(s) based on specific VLAN Groups, but we can't from [dcim/interfaces/](https://demo.netbox.dev/dcim/interfaces). Here's the workflow: 1. Create a device. 2. Assign the device to a virtualization cluster. 3. Create a VLAN group attached to the cluster. 4. Create VLAN(s) in the VLAN group. 5. Can't assign VLAN(s) from the VLAN group on the device interfaces manually in the GUI. 6. Can assign VLAN(s) using the API or a Netbox Scripts. When we modify an interface and want to assign a VLAN based on a VLAN group, the "dropdown menu/list" of Untagged VLAN and Tagged VLANs is empty even if VLANs exist in the selected VLAN group. ![Image](https://github.com/user-attachments/assets/abd1c15b-9b31-433c-b2b8-522e1893f7f7) ### Use case We are allowed to create VLANs and VLAN groups, we should be able to assign any of those VLANs in the Netbox Web UI. Creating VLAN groups is common in virtualization or when we group devices that shares VLANs: VTP domain (people still uses those), any Network Fabric or cluster of devices (or servers). ### Database changes I don't think any database change is required, the API already allows proper assignment of VLANs that are member of a group. This is actually how we work around the issue at the moment: we have created a form with a Netbox Scripts that allows us to add/remove VLANs to an interface manually. We override the UI limitation. I feel the current limitation, is mainly due to the Web UI vlan lookup logic: when selecting a VLAN group, the list/dropdown is empty (the query may need to be fine tuned). ### External dependencies N/A
adam added the type: featurecomplexity: mediumnetboxstatus: backlog labels 2025-12-29 21:39:50 +01:00
adam commented 2025-12-29 21:39:51 +01:00
Author
Owner
Copy Link

@19rwk82 commented on GitHub (May 9, 2025):

There was a pull request a few weeks ago which fixes this for us -> https://github.com/netbox-community/netbox/pull/19093
Unfortunately it was closed...

@19rwk82 commented on GitHub (May 9, 2025): There was a pull request a few weeks ago which fixes this for us -> https://github.com/netbox-community/netbox/pull/19093 Unfortunately it was closed...
adam commented 2025-12-29 21:39:51 +01:00
Author
Owner
Copy Link

@awerner commented on GitHub (Jun 2, 2025):

I also ran into this issue. Is there any way to get #19093 updated to reference this issue instead? It should be easy to get this implemented, as the pull request is already there, but was unfortunately closed.

@awerner commented on GitHub (Jun 2, 2025): I also ran into this issue. Is there any way to get #19093 updated to reference this issue instead? It should be easy to get this implemented, as the pull request is already there, but was unfortunately closed.
adam commented 2025-12-29 21:39:51 +01:00
Author
Owner
Copy Link

@19rwk82 commented on GitHub (Jun 2, 2025):

This seems to have been implemented with another PR (https://github.com/netbox-community/netbox/pull/19485) which has already been merged... So waiting for 4.3.2 :)

@19rwk82 commented on GitHub (Jun 2, 2025): This seems to have been implemented with another PR (https://github.com/netbox-community/netbox/pull/19485) which has already been merged... So waiting for 4.3.2 :)
adam commented 2025-12-29 21:39:51 +01:00
Author
Owner
Copy Link

@SteveRodrigue commented on GitHub (Oct 11, 2025):

This seems to have been implemented with another PR (https://github.com/netbox-community/netbox/pull/19485) which has already been merged... So waiting for 4.3.2 :)

I just tested the scenario on 4.4.2 demo version and even if I selected VLAN GROUP, the drop down menu don't allow to select a vlan from this group.

image

@SteveRodrigue commented on GitHub (Oct 11, 2025): > This seems to have been implemented with another PR (https://github.com/netbox-community/netbox/pull/19485) which has already been merged... So waiting for 4.3.2 :) I just tested the scenario on 4.4.2 demo version and even if I selected VLAN GROUP, the drop down menu don't allow to select a vlan from this group. ![image](https://github.com/user-attachments/assets/cb9b94ce-1cb6-4412-93ed-e85457dd3a7f)
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 complexity: medium netbox status: backlog type: feature
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#11070
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?