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

VLAN Groups not visible in site groups #8736

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

Originally created by @chuegel on GitHub (Oct 10, 2023).

NetBox version

v3.5.8

Python version

3.9

Steps to Reproduce

We want to assing a VLAN Group to multiple sites as these VLAN name/ids are the same on each of this site.

  1. Create a site group
  2. Create a VLAN Group:
    • Min VLAN ID: 1000
    • Max VLAN ID: 1020
    • Scope: DCIM > Site Group
    • Site Group <assign group created in 1>
  3. Add VLANs to this group and assign VLAN Group create in 2
  4. Edit a site and add group created in 1
  5. no VLAN Group is visible

Am I missing something?

Expected Behavior

Assigned VLANS from VLAN Group to site group should be visible

Observed Behavior

see above

Originally created by @chuegel on GitHub (Oct 10, 2023). ### NetBox version v3.5.8 ### Python version 3.9 ### Steps to Reproduce We want to assing a VLAN Group to multiple sites as these VLAN name/ids are the same on each of this site. 1. Create a site group 2. Create a VLAN Group: - Min VLAN ID: 1000 - Max VLAN ID: 1020 - Scope: DCIM > Site Group - Site Group <assign group created in 1> 3. Add VLANs to this group and assign VLAN Group create in 2 4. Edit a site and add group created in 1 5. no VLAN Group is visible Am I missing something? ### Expected Behavior Assigned VLANS from VLAN Group to site group should be visible ### Observed Behavior see above
adam added the type: bug label 2025-12-29 20:40:35 +01:00
adam closed this issue 2025-12-29 20:40:35 +01:00
adam commented 2025-12-29 20:40:36 +01:00
Author
Owner
Copy Link

@DanSheps commented on GitHub (Oct 11, 2023):

If you are referring to the "VLAN Groups" display, that is for VLAN Groups specifically assigned to the site (Scope -> Site)

@DanSheps commented on GitHub (Oct 11, 2023): If you are referring to the "VLAN Groups" display, that is for VLAN Groups specifically assigned to the site (Scope -> Site)
adam commented 2025-12-29 20:40:36 +01:00
Author
Owner
Copy Link

@DanSheps commented on GitHub (Oct 11, 2023):

Thank you for opening a bug report. It seems that the described functionality is intended behavior. If you meant to open a feature request instead, please close this issue and open a new one using the feature request template. Otherwise, please revise your post above to elaborate on why you believe the observed behavior is flawed.

@DanSheps commented on GitHub (Oct 11, 2023): Thank you for opening a bug report. It seems that the described functionality is intended behavior. If you meant to open a feature request instead, please close this issue and open a new one using the [feature request template](https://github.com/netbox-community/netbox/issues/new?template=feature_request.md). Otherwise, please revise your post above to elaborate on why you believe the observed behavior is flawed.
adam commented 2025-12-29 20:40:37 +01:00
Author
Owner
Copy Link

@chuegel commented on GitHub (Oct 12, 2023):

@DanSheps thanks for your reply.
Well, no, basically we want to assign a group of defined vlans to a site group since those sites share the same VLAN IDs and names.
But if VLAN Group has a scope site group those sites in that group do not get the VLANs assigned

@chuegel commented on GitHub (Oct 12, 2023): @DanSheps thanks for your reply. Well, no, basically we want to assign a group of defined vlans to a site group since those sites share the same VLAN IDs and names. But if VLAN Group has a scope site group those sites in that group do not get the VLANs assigned
adam commented 2025-12-29 20:40:37 +01:00
Author
Owner
Copy Link

@DanSheps commented on GitHub (Oct 12, 2023):

I think you are missing the point, those sites don't have them assigned because the scope is the site group.

If you go to a device in one of those sites it will be visible still because the device the site is a member of is part of the site group, but you won't see it on the site detail itself because it is not directly assigned to the site.

If you need further assistance, please open a help discussion post.

@DanSheps commented on GitHub (Oct 12, 2023): I think you are missing the point, those sites don't have them assigned because the scope is the site group. If you go to a device in one of those sites it will be visible still because the device the site is a member of is part of the site group, but you won't see it on the site detail itself because it is not directly assigned to the site. If you need further assistance, please open a help discussion post.
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 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#8736
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?