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

Parent/Child Prefixes not belonging to the same VRF #3773

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

Originally created by @xjs678qr on GitHub (Jun 11, 2020).

Environment

Python version: 3.6.9
NetBox version: 2.8.5

Steps to Reproduce

Create a container prefix in IPAM in the Global VRF (10.8.0.0/13) for Tenant A.
Create a container prefix in IPAM in the VRF 'Branches' (10.8.128.0/19) for Tenant A.

Expected Behavior

The child prefix 10.8.128.0/19 is considered as a child prefix of 10.8.0.0/13 and de-counted from the available IP space in 10.8.0.0/13.

Observed Behavior

When opening 10.8.0.0/13, 10.8.128.0/19 is listed amongst the child prefixes. However, the utilization for 10.8.0.0/13 is listed as 0% and in the collapsed prefix view, 10.8.128.0/19 is listed at top level.
If I alter 10.8.0.0/13 to the same VRF ('Branches') as 10.8.128.0/19, the utilization is calculated as exptected.

Originally created by @xjs678qr on GitHub (Jun 11, 2020). ### Environment Python version: 3.6.9 NetBox version: 2.8.5 ### Steps to Reproduce Create a container prefix in IPAM in the Global VRF (10.8.0.0/13) for Tenant A. Create a container prefix in IPAM in the VRF 'Branches' (10.8.128.0/19) for Tenant A. ### Expected Behavior The child prefix 10.8.128.0/19 is considered as a child prefix of 10.8.0.0/13 and de-counted from the available IP space in 10.8.0.0/13. ### Observed Behavior When opening 10.8.0.0/13, 10.8.128.0/19 is listed amongst the child prefixes. However, the utilization for 10.8.0.0/13 is listed as 0% and in the collapsed prefix view, 10.8.128.0/19 is listed at top level. If I alter 10.8.0.0/13 to the same VRF ('Branches') as 10.8.128.0/19, the utilization is calculated as exptected.
adam added the status: duplicate label 2025-12-29 18:31:09 +01:00
adam closed this issue 2025-12-29 18:31:09 +01:00
adam commented 2025-12-29 18:31:09 +01:00
Author
Owner
Copy Link

@jsenecal commented on GitHub (Jun 14, 2020):

Hi @xjs678qr, could this be related to what is discussed there? https://github.com/netbox-community/netbox/issues/1073 or there? https://github.com/netbox-community/netbox/issues/2562

@jsenecal commented on GitHub (Jun 14, 2020): Hi @xjs678qr, could this be related to what is discussed there? https://github.com/netbox-community/netbox/issues/1073 or there? https://github.com/netbox-community/netbox/issues/2562
adam commented 2025-12-29 18:31:10 +01:00
Author
Owner
Copy Link

@DanSheps commented on GitHub (Jun 15, 2020):

It is a duplicate of #2562

The reason for it is the way we count IP prefixes and VRF membership. In an effort to be as efficient as possible, we maintain a list of VRF's and pop the VRF once we "exit" that VRF, so if you have:

  • 10.8.0.0/13, VRF: Global
  • 10.8.0.0/19 VRF: Branches
  • 10.8.1.0/24 VRF: Global
  • 10.8.128.0/19 VRF: Branches

By the time we hit "branches" we have already exited the VRF. There will be some new logic eventually, but not quite yet as it is quite involved.

@DanSheps commented on GitHub (Jun 15, 2020): It is a duplicate of #2562 The reason for it is the way we count IP prefixes and VRF membership. In an effort to be as efficient as possible, we maintain a list of VRF's and pop the VRF once we "exit" that VRF, so if you have: * 10.8.0.0/13, VRF: Global * 10.8.0.0/19 VRF: Branches * 10.8.1.0/24 VRF: Global * 10.8.128.0/19 VRF: Branches By the time we hit "branches" we have already exited the VRF. There will be some new logic eventually, but not quite yet as it is quite involved.
adam commented 2025-12-29 18:31:10 +01:00
Author
Owner
Copy Link

@DanSheps commented on GitHub (Jun 15, 2020):

Duplicate of #2562

@DanSheps commented on GitHub (Jun 15, 2020): Duplicate of #2562
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 status: duplicate
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#3773
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?