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

Site Groups are missing VLAN and VM related objects #10884

New Issue
Closed
opened 2025-12-29 21:37:15 +01:00 by adam · 1 comment
adam commented 2025-12-29 21:37:15 +01:00
Owner
Copy Link

Originally created by @artiomello on GitHub (Mar 12, 2025).

Originally assigned to: @renatoalmeidaoliveira on GitHub.

Deployment Type

Self-hosted

NetBox Version

v.4.2.4

Python Version

3.10

Steps to Reproduce

  1. Create a Site Group "Example Site Group"
  2. Create a VLAN group "Example VLAN Group" with scope "DCIM > Site Group"
  3. Assign the VLAN group to the "Example Site Group"
  4. Create the VLAN group
  5. Go to Site Groups
  6. See that there is no reference to any VLANs or VLAN groups even though it's literally the only parent object that has been selected for the created VLAN group

Expected Behavior

Site groups should reference the same related objects as Sites, and not just a subset of them. That way it would be not only useful but also possible to see all:

  • VLANs
  • VLAN Groups
  • Virtual Machines
  • ASNs
  • Clusters
  • Devices

that are present within a Site Group.

Observed Behavior

Here's a screenshot of a Site's related objects, that is part of a Site Group:

Image

Note the highlighted related objects.

Now, here's a screenshot of a Site Group's (where the above Site is a member of) related objects:

Image

Notice the following objects mising:

  • VLANs
  • VLAN Groups
  • Virtual Machines
  • ASNs
  • Clusters
  • Devices
Originally created by @artiomello on GitHub (Mar 12, 2025). Originally assigned to: @renatoalmeidaoliveira on GitHub. ### Deployment Type Self-hosted ### NetBox Version v.4.2.4 ### Python Version 3.10 ### Steps to Reproduce 1. Create a Site Group "Example Site Group" 2. Create a VLAN group "Example VLAN Group" with scope "DCIM > Site Group" 3. Assign the VLAN group to the "Example Site Group" 4. Create the VLAN group 5. Go to Site Groups 6. See that there is no reference to any VLANs or VLAN groups even though it's literally the only parent object that has been selected for the created VLAN group ### Expected Behavior Site groups should reference the same related objects as Sites, and not just a subset of them. That way it would be not only useful but also possible to see all: - VLANs - VLAN Groups - Virtual Machines - ASNs - Clusters - Devices that are present within a Site Group. ### Observed Behavior Here's a screenshot of a `Site's` related objects, that is part of a Site Group: ![Image](https://github.com/user-attachments/assets/7d562b32-da67-415f-bd4a-044df1a9758b) Note the highlighted related objects. Now, here's a screenshot of a `Site Group's` (where the above Site is a member of) related objects: ![Image](https://github.com/user-attachments/assets/2a991f19-052d-477f-abec-05bf990b4c00) Notice the following objects mising: - VLANs - VLAN Groups - Virtual Machines - ASNs - Clusters - Devices
adam added the type: bugstatus: acceptedseverity: low labels 2025-12-29 21:37:15 +01:00
adam closed this issue 2025-12-29 21:37:15 +01:00
adam commented 2025-12-29 21:37:16 +01:00
Author
Owner
Copy Link

@renatoalmeidaoliveira commented on GitHub (Mar 18, 2025):

Blocked by #18933 and #18939

@renatoalmeidaoliveira commented on GitHub (Mar 18, 2025): Blocked by #18933 and #18939
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#10884
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?