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

Utilization threshold is wrong #7399

New Issue
Closed
opened 2025-12-29 20:22:57 +01:00 by adam · 4 comments
adam commented 2025-12-29 20:22:57 +01:00
Owner
Copy Link

Originally created by @alexandredpy on GitHub (Dec 21, 2022).

NetBox version

v3.4.1

Python version

3.9

Steps to Reproduce

  1. Go on IPAM > Prefixes

Expected Behavior

The gauge should be fully filled in grey (100.0%)

Observed Behavior

My subnet is an IPv4 /30, so 2 usable adresses. 2 IP addresses are currently assigned, so the subnet is 100% used. The utilization percentage is seen as 100,0% but the threshold is not correctly displayed.
The gauge is not totally filled in grey

See screenshot
image

However, seems to work correctly on a /126 IPv6 subnet

Originally created by @alexandredpy on GitHub (Dec 21, 2022). ### NetBox version v3.4.1 ### Python version 3.9 ### Steps to Reproduce 1. Go on IPAM > Prefixes ### Expected Behavior The gauge should be fully filled in grey (100.0%) ### Observed Behavior My subnet is an IPv4 /30, so 2 usable adresses. 2 IP addresses are currently assigned, so the subnet is 100% used. The utilization percentage is seen as 100,0% but the threshold is not correctly displayed. The gauge is not totally filled in grey See screenshot ![image](https://user-images.githubusercontent.com/18117508/208894700-d5537ec3-979e-4aa9-bc1e-bff87be0b0fc.png) However, seems to work correctly on a /126 IPv6 subnet
adam added the type: bugstatus: duplicate labels 2025-12-29 20:22:58 +01:00
adam closed this issue 2025-12-29 20:22:58 +01:00
adam commented 2025-12-29 20:22:58 +01:00
Author
Owner
Copy Link

@julianstolp commented on GitHub (Dec 21, 2022):

I can confirm this in our testing instance. It also applies to the rack utilization.

@julianstolp commented on GitHub (Dec 21, 2022): I can confirm this in our testing instance. It also applies to the rack utilization.
adam commented 2025-12-29 20:22:58 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Dec 22, 2022):

Thank you for opening a bug report. Unfortunately, the information you have provided is not sufficient for someone else to attempt to reproduce the reported behavior. Remember, each bug report must include detailed steps that someone else can follow on a clean, empty NetBox installation to reproduce the exact problem you're experiencing. These instructions should include the creation of any involved objects, any configuration changes, and complete accounting of the actions being taken. Also be sure that your report does not reference data on the public NetBox demo, as that is subject to change at any time by an outside party and cannot be relied upon for bug reports.

@jeremystretch commented on GitHub (Dec 22, 2022): Thank you for opening a bug report. Unfortunately, the information you have provided is not sufficient for someone else to attempt to reproduce the reported behavior. Remember, each bug report must include detailed steps that someone else can follow on a clean, empty NetBox installation to reproduce the exact problem you're experiencing. These instructions should include the creation of any involved objects, any configuration changes, and complete accounting of the actions being taken. Also be sure that your report does not reference data on the public NetBox demo, as that is subject to change at any time by an outside party and cannot be relied upon for bug reports.
adam commented 2025-12-29 20:22:58 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Dec 22, 2022):

Duplicate of #11271

@jeremystretch commented on GitHub (Dec 22, 2022): Duplicate of #11271
adam commented 2025-12-29 20:22:59 +01:00
Author
Owner
Copy Link

@aurus686 commented on GitHub (Jan 9, 2023):

Дубликат № 11271

Thanks! Upgrading to version 3.4.2 helped!

@aurus686 commented on GitHub (Jan 9, 2023): > Дубликат [№ 11271](https://github.com/netbox-community/netbox/issues/11271) Thanks! Upgrading to version 3.4.2 helped!
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 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#7399
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?