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 assign VLAN group to Device Interface #10278

New Issue
Closed
opened 2025-12-29 21:29:18 +01:00 by adam · 2 comments
adam commented 2025-12-29 21:29:18 +01:00
Owner
Copy Link

Originally created by @c-po on GitHub (Sep 23, 2024).

Originally assigned to: @arthanson on GitHub.

Deployment Type

NetBox Cloud

NetBox Version

v4.1.1

Python Version

3.10

Steps to Reproduce

  1. Create a new device e.g. Cisco ISR1111-8P in JBB Branch 109 site

  2. Create new Interface configuration on said new device

  3. Add VLAN Group to tagged port
    image

  4. Save confiruration change -> You will see a green modified banner on the bottom right
    image

Nothing has been changed on that interface.

Expected Behavior

The newly assigned VLAN group should be displayed as part of the interface configuration

Observed Behavior

Requested change in Port configuration is not applied.

The changelog just states that tagging was activated for the port in question

image

Originally created by @c-po on GitHub (Sep 23, 2024). Originally assigned to: @arthanson on GitHub. ### Deployment Type NetBox Cloud ### NetBox Version v4.1.1 ### Python Version 3.10 ### Steps to Reproduce 1. Create a new device e.g. Cisco ISR1111-8P in `JBB Branch 109` site 2. Create new Interface configuration on said new device 3. Add VLAN Group to tagged port ![image](https://github.com/user-attachments/assets/0fc0294a-7d26-4da1-ac3a-add577b393dd) 4. Save confiruration change -> You will see a green modified banner on the bottom right ![image](https://github.com/user-attachments/assets/0aed4189-b9db-4257-b474-37ba86d8278a) Nothing has been changed on that interface. ### Expected Behavior The newly assigned VLAN group should be displayed as part of the interface configuration ### Observed Behavior Requested change in Port configuration is not applied. The changelog just states that tagging was activated for the port in question ![image](https://github.com/user-attachments/assets/2dc016e6-57b0-416f-81e4-9c259668f391)
adam added the type: bugstatus: acceptedseverity: low labels 2025-12-29 21:29:18 +01:00
adam closed this issue 2025-12-29 21:29:18 +01:00
adam commented 2025-12-29 21:29:19 +01:00
Author
Owner
Copy Link

@arthanson commented on GitHub (Sep 23, 2024):

The vlan_group is actually just for filtering the tagged and untagged vlans, it isn't stored. Probably should have a help-text to clarify that.

@arthanson commented on GitHub (Sep 23, 2024): The vlan_group is actually just for filtering the tagged and untagged vlans, it isn't stored. Probably should have a help-text to clarify that.
adam commented 2025-12-29 21:29:19 +01:00
Author
Owner
Copy Link

@c-po commented on GitHub (Sep 23, 2024):

I guess it would be a super cool feature to do so, too - if it's not yet supported.

Imagine I have a bunch of Hypervisor nodes all consume the same set of VLANs. It would be easier to simply select the VLAN group. And if I need an additional VLAN, I just add it to the VLAN group.

That simplifies the single source of truth.

@c-po commented on GitHub (Sep 23, 2024): I guess it would be a super cool feature to do so, too - if it's not yet supported. Imagine I have a bunch of Hypervisor nodes all consume the same set of VLANs. It would be easier to simply select the VLAN group. And if I need an additional VLAN, I just add it to the VLAN group. That simplifies the single source of truth.
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 severity: low 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#10278
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?