Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Unable to assign VLAN group to Device Interface #17569

Closed
c-po opened this issue Sep 23, 2024 · 2 comments · Fixed by #17578
Closed

Unable to assign VLAN group to Device Interface #17569

c-po opened this issue Sep 23, 2024 · 2 comments · Fixed by #17578
Assignees
@arthanson
Labels
severity: low Does not significantly disrupt application functionality, or a workaround is available status: accepted This issue has been accepted for implementation type: bug A confirmed report of unexpected behavior in the application

Comments

@c-po
Copy link

c-po commented Sep 23, 2024 •
edited by jeremystretch
Loading

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
@c-po c-po added status: needs triage This issue is awaiting triage by a maintainer type: bug A confirmed report of unexpected behavior in the application labels Sep 23, 2024
@arthanson arthanson added status: needs owner This issue is tentatively accepted pending a volunteer committed to its implementation severity: medium Results in substantial degraded or broken functionality for specfic workflows status: accepted This issue has been accepted for implementation and removed status: needs triage This issue is awaiting triage by a maintainer status: needs owner This issue is tentatively accepted pending a volunteer committed to its implementation labels Sep 23, 2024
@arthanson arthanson self-assigned this Sep 23, 2024
@arthanson arthanson added severity: low Does not significantly disrupt application functionality, or a workaround is available and removed severity: medium Results in substantial degraded or broken functionality for specfic workflows labels Sep 23, 2024
@arthanson
Copy link
Collaborator

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 arthanson mentioned this issue Sep 23, 2024
Merged
@c-po
Copy link
Author

c-po commented 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 up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@arthanson arthanson

Labels
severity: low Does not significantly disrupt application functionality, or a workaround is available status: accepted This issue has been accepted for implementation type: bug A confirmed report of unexpected behavior in the application
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

17569 Add help text to VLAN Group that is not saved on the interface netbox-community/netbox
2 participants
@arthanson @c-po