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

IP range utilization bar being rounded down #9388

New Issue
Closed
opened 2025-12-29 20:49:13 +01:00 by adam · 0 comments
adam commented 2025-12-29 20:49:13 +01:00
Owner
Copy Link

Originally created by @Azmodeszer on GitHub (Mar 25, 2024).

Originally assigned to: @arthanson on GitHub.

Deployment Type

Self-hosted

NetBox Version

v3.7.4

Python Version

3.10

Steps to Reproduce

The utilization bar for IP ranges is not behaving the same way as for prefixes. Decimal digits are apparently being rounded down to the next integer.

  1. Create an IP range, let's say 1.1.1.1-254/24.
  2. Create an IP in that range.

Expected Behavior

Utilization shows 0.4% (and indeed this is shown for the prefix without the range and only the solitary IP).

2 IPs 0.8%
3 IPs 1.2%
etc.

Observed Behavior

Utilization shows 0.0%.

2 IPs 0.0%
3 IPs 1.0%
etc.

Originally created by @Azmodeszer on GitHub (Mar 25, 2024). Originally assigned to: @arthanson on GitHub. ### Deployment Type Self-hosted ### NetBox Version v3.7.4 ### Python Version 3.10 ### Steps to Reproduce The utilization bar for IP ranges is not behaving the same way as for prefixes. Decimal digits are apparently being rounded down to the next integer. 1. Create an IP range, let's say 1.1.1.1-254/24. 2. Create an IP in that range. ### Expected Behavior Utilization shows 0.4% (and indeed this is shown for the **prefix** without the range and only the solitary IP). 2 IPs 0.8% 3 IPs 1.2% etc. ### Observed Behavior Utilization shows 0.0%. 2 IPs 0.0% 3 IPs 1.0% etc.
adam added the type: bugstatus: acceptedseverity: low labels 2025-12-29 20:49:13 +01:00
adam closed this issue 2025-12-29 20:49:13 +01:00
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#9388
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?