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

IPAM does not show all available prefixes #9403

New Issue
Closed
opened 2025-12-29 20:49:22 +01:00 by adam · 1 comment
adam commented 2025-12-29 20:49:22 +01:00
Owner
Copy Link

Originally created by @abrahamvegh on GitHub (Mar 28, 2024).

Deployment Type

Self-hosted

NetBox Version

3.7.4

Python Version

3.11

Steps to Reproduce

Create this example set of child prefixes under 10.35.96.0/20:
Screenshot 2024-03-28 at 9 37 39 AM

Expected Behavior

In the example shown, 10.35.102.0/23 has prefix space available, so I would expect it to be displayed here, as it is in the detail view for that prefix.
Screenshot 2024-03-28 at 9 39 38 AM

Observed Behavior

The available prefix space is not shown.

Originally created by @abrahamvegh on GitHub (Mar 28, 2024). ### Deployment Type Self-hosted ### NetBox Version 3.7.4 ### Python Version 3.11 ### Steps to Reproduce Create this example set of child prefixes under `10.35.96.0/20`: <img width="361" alt="Screenshot 2024-03-28 at 9 37 39 AM" src="https://github.com/netbox-community/netbox/assets/53161/26dfc7f7-71ff-4ff4-aaba-c53badefcfb1"> ### Expected Behavior In the example shown, `10.35.102.0/23` has prefix space available, so I would expect it to be displayed here, as it is in the detail view for that prefix. <img width="317" alt="Screenshot 2024-03-28 at 9 39 38 AM" src="https://github.com/netbox-community/netbox/assets/53161/369b0c81-e338-47e1-9ab7-bb07cf634419"> ### Observed Behavior The available prefix space is not shown.
adam closed this issue 2025-12-29 20:49:22 +01:00
adam commented 2025-12-29 20:49:23 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Mar 28, 2024):

This is the intended behavior. 10.35.103.0/24 is not listed as available space for 10.35.96.0/20 because it is claimed by the 10.35.102.0/23 container. It is listed as available space only within that container. If you were to delete the container, 10.35.103.0/24 would be listed as available space directly beneath 10.35.96.0/20.

@jeremystretch commented on GitHub (Mar 28, 2024): This is the intended behavior. 10.35.103.0/24 is not listed as available space for 10.35.96.0/20 because it is claimed by the 10.35.102.0/23 container. It is listed as available space only _within that container_. If you were to delete the container, 10.35.103.0/24 would be listed as available space directly beneath 10.35.96.0/20.
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#9403
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?