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

Aggregate utilization should consider a prefix of type "container"'s utilization in the calculation instead of assuming 100% #7633

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

Originally created by @BrunoBlanes on GitHub (Feb 11, 2023).

NetBox version

v3.4.4

Python version

3.8

Steps to Reproduce

  1. Create an aggregate of subnet mask /23 or higher
  2. Create prefixes with subnet mask /24 and set them as containers

Expected Behavior

Expected aggregate utilization to be based on prefixes created, except when using containers, in which case utilization should take into consideration the container's utiliation.

Observed Behavior

Aggregate utilization goes to 100%.

Originally created by @BrunoBlanes on GitHub (Feb 11, 2023). ### NetBox version v3.4.4 ### Python version 3.8 ### Steps to Reproduce 1. Create an aggregate of subnet mask /23 or higher 2. Create prefixes with subnet mask /24 and set them as containers ### Expected Behavior Expected aggregate utilization to be based on prefixes created, except when using containers, in which case utilization should take into consideration the container's utiliation. ### Observed Behavior Aggregate utilization goes to 100%.
adam closed this issue 2025-12-29 20:26:18 +01:00
adam commented 2025-12-29 20:26:19 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Feb 11, 2023):

This is expected behavior. If you would like to propose a change, please submit a feature request citing your use case.

@jeremystretch commented on GitHub (Feb 11, 2023): This is expected behavior. If you would like to propose a change, please submit a [feature request](https://github.com/netbox-community/netbox/issues/new?assignees=&labels=type%3A+feature&template=feature_request.yaml) citing your use case.
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#7633
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?