Skip to content

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

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.

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

Open
SteveRodrigue opened this issue Apr 22, 2025 · 1 comment
Labels
complexity: medium Requires a substantial but not unusual amount of effort to implement status: backlog Awaiting selection for work type: feature Introduction of new functionality to the application

Comments

@SteveRodrigue
Copy link

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

@SteveRodrigue SteveRodrigue added status: needs triage This issue is awaiting triage by a maintainer type: feature Introduction of new functionality to the application labels Apr 22, 2025
@jeremystretch jeremystretch added status: backlog Awaiting selection for work complexity: medium Requires a substantial but not unusual amount of effort to implement and removed status: needs triage This issue is awaiting triage by a maintainer labels Apr 24, 2025
@19rwk82
Copy link

19rwk82 commented May 9, 2025

There was a pull request a few weeks ago which fixes this for us -> #19093
Unfortunately it was closed...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
complexity: medium Requires a substantial but not unusual amount of effort to implement status: backlog Awaiting selection for work type: feature Introduction of new functionality to the application
Projects
None yet
Development

No branches or pull requests

3 participants