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

Mark Utilized IP Range not decreased from IP Prefix #11199

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

Originally created by @magedelmalah on GitHub (May 19, 2025).

Originally assigned to: @arthanson on GitHub.

Deployment Type

NetBox Cloud

NetBox Version

v4.3.1

Python Version

3.10

Steps to Reproduce

  1. Create IP prefix (for example 12.12.13.0/24)
  2. Check the "Available IPs" for IP prefix
  3. Create IP range (start 12.12.13.1/24 end 12.12.13.50/24) and mark it as utilized
  4. Check the "Available IPs" for IP prefix and you will notice that no change in the number of "Available IPs"

Expected Behavior

When IP range created and marked as utilized, the available IPs in IP Prefix should be decreased with the same number of host IP range in IP Range

Observed Behavior

notice that no change in the number of "Available IPs" for IP Prefix after creating IP Range

Originally created by @magedelmalah on GitHub (May 19, 2025). Originally assigned to: @arthanson on GitHub. ### Deployment Type NetBox Cloud ### NetBox Version v4.3.1 ### Python Version 3.10 ### Steps to Reproduce 1. Create IP prefix (for example 12.12.13.0/24) 2. Check the "Available IPs" for IP prefix 3. Create IP range (start 12.12.13.1/24 end 12.12.13.50/24) and mark it as utilized 4. Check the "Available IPs" for IP prefix and you will notice that no change in the number of "Available IPs" ### Expected Behavior When IP range created and marked as utilized, the available IPs in IP Prefix should be decreased with the same number of host IP range in IP Range ### Observed Behavior notice that no change in the number of "Available IPs" for IP Prefix after creating IP Range
adam added the type: bugstatus: acceptedseverity: low labels 2025-12-29 21:41:49 +01:00
adam closed this issue 2025-12-29 21:41:50 +01:00
adam commented 2025-12-29 21:41:50 +01:00
Author
Owner
Copy Link

@arthanson commented on GitHub (Jun 4, 2025):

This is actually by design, if you look at mark utilized on IP Range it states "Affects utilization calculation without restricting new IPs" You can set mark populated to remove it from the Available IPs.

@arthanson commented on GitHub (Jun 4, 2025): This is actually by design, if you look at mark utilized on IP Range it states "Affects utilization calculation without restricting new IPs" You can set mark populated to remove it from the Available IPs.
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#11199
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?