Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

IP range utilization bar being rounded down #15524

Closed
Azmodeszer opened this issue Mar 25, 2024 · 0 comments · Fixed by #15734
Closed

IP range utilization bar being rounded down #15524

Azmodeszer opened this issue Mar 25, 2024 · 0 comments · Fixed by #15734
Assignees
@arthanson
Labels
severity: low Does not significantly disrupt application functionality, or a workaround is available status: accepted This issue has been accepted for implementation type: bug A confirmed report of unexpected behavior in the application

Comments

@Azmodeszer
Copy link
Contributor

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.
@Azmodeszer Azmodeszer added status: needs triage This issue is awaiting triage by a maintainer type: bug A confirmed report of unexpected behavior in the application labels Mar 25, 2024
@Azmodeszer Azmodeszer changed the title IP range utlization bar rounded down IP range utilization bar being rounded down Mar 25, 2024
@abhi1693 abhi1693 added status: needs owner This issue is tentatively accepted pending a volunteer committed to its implementation severity: low Does not significantly disrupt application functionality, or a workaround is available and removed status: needs triage This issue is awaiting triage by a maintainer labels Apr 5, 2024
@abhi1693 abhi1693 removed their assignment Apr 5, 2024
@arthanson arthanson self-assigned this Apr 16, 2024
@arthanson arthanson removed the status: needs owner This issue is tentatively accepted pending a volunteer committed to its implementation label Apr 16, 2024
@arthanson arthanson mentioned this issue Apr 16, 2024
Merged
@jeremystretch jeremystretch added the status: accepted This issue has been accepted for implementation label Apr 29, 2024
jeremystretch added a commit that referenced this issue Apr 29, 2024
@jeremystretch
Changelog for #14852, #15428, #15524, #15548, #15812, #15845, #15872
693c6e4
@jeremystretch jeremystretch mentioned this issue May 1, 2024
Merged
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Jul 29, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@arthanson arthanson

Labels
severity: low Does not significantly disrupt application functionality, or a workaround is available status: accepted This issue has been accepted for implementation type: bug A confirmed report of unexpected behavior in the application
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

15524 round iprange utilization netbox-community/netbox
4 participants
@arthanson @abhi1693 @jeremystretch @Azmodeszer