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

Assigning a Site Group to a IPAM Prefix does nothing #5704

New Issue
Closed
opened 2025-12-29 19:31:39 +01:00 by adam · 3 comments
adam commented 2025-12-29 19:31:39 +01:00
Owner
Copy Link

Originally created by @soer7022 on GitHub (Nov 24, 2021).

NetBox version

v3.0.10 & 2.11.9

Python version

3.9

Steps to Reproduce

  1. Create a prefix and a site group
  2. Click edit on the prefix
  3. Assign the site group to the prefix
  4. Click save
  5. Click edit on the prefix
  6. Notice that the prefix is not assigned to the site group

Expected Behavior

I expect the Prefix to be assigned to the site group. And if this is not possible I at least expect to get an error

Observed Behavior

No error, it just accepts and nothing happens

Originally created by @soer7022 on GitHub (Nov 24, 2021). ### NetBox version v3.0.10 & 2.11.9 ### Python version 3.9 ### Steps to Reproduce 1. Create a prefix and a site group 2. Click edit on the prefix 3. Assign the site group to the prefix 4. Click save 5. Click edit on the prefix 6. Notice that the prefix is not assigned to the site group ### Expected Behavior I expect the Prefix to be assigned to the site group. And if this is not possible I at least expect to get an error ### Observed Behavior No error, it just accepts and nothing happens
adam closed this issue 2025-12-29 19:31:39 +01:00
adam commented 2025-12-29 19:31:39 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Nov 24, 2021):

Prefixes cannot be assigned to site groups. The site group field exists solely as a filter for the site field.

@jeremystretch commented on GitHub (Nov 24, 2021): Prefixes cannot be assigned to site groups. The site group field exists solely as a filter for the site field.
adam commented 2025-12-29 19:31:40 +01:00
Author
Owner
Copy Link

@zacho112 commented on GitHub (Nov 24, 2021):

Would it be an idea to add a scope to the prefixes like on VLANs? Eg. if you have a L2 network across multiple "sites"/buildings, you might need to document the device on site X but the VLAN/Prefixes etc. is on site A, which actually terminates the L3 info, which could be mapped to a site-group, instead of that site, so all "subsites" are able to fetch the info, without hardcoding anything.

@zacho112 commented on GitHub (Nov 24, 2021): Would it be an idea to add a scope to the prefixes like on VLANs? Eg. if you have a L2 network across multiple "sites"/buildings, you might need to document the device on site X but the VLAN/Prefixes etc. is on site A, which actually terminates the L3 info, which could be mapped to a site-group, instead of that site, so all "subsites" are able to fetch the info, without hardcoding anything.
adam commented 2025-12-29 19:31:40 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Nov 24, 2021):

Would it be an idea to add a scope to the prefixes like on VLANs?

This has been proposed under #6414.

@jeremystretch commented on GitHub (Nov 24, 2021): > Would it be an idea to add a scope to the prefixes like on VLANs? This has been proposed under #6414.
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
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#5704
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?