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

VLANGroup utilization is not reported accurately #17306

Closed
jeremystretch opened this issue Aug 29, 2024 · 0 comments
Closed

VLANGroup utilization is not reported accurately #17306

jeremystretch opened this issue Aug 29, 2024 · 0 comments
Assignees
@arthanson
Labels
beta Concerns a bug/feature in a beta release 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

@jeremystretch
Copy link
Member

Deployment Type

NetBox Cloud

NetBox Version

v4.1-beta1

Python Version

3.10

Steps to Reproduce

  1. Create a VLAN group allowing VIDs 1 through 200 (inclusive)
  2. Create a VLAN with VID 1 inside the group
  3. View the group's utilization

Expected Behavior

The VLAN group should report a utilization of 0.5% (1 / 200).

Observed Behavior

The VLAN group utilization is reported as 0.0%.

If we change the group's VLAN range to 1-100 (inclusive), its utilization is then reported as 1.0%.
@jeremystretch jeremystretch added type: bug A confirmed report of unexpected behavior in the application status: needs owner This issue is tentatively accepted pending a volunteer committed to its implementation beta Concerns a bug/feature in a beta release severity: low Does not significantly disrupt application functionality, or a workaround is available labels Aug 29, 2024
@arthanson arthanson removed the status: needs owner This issue is tentatively accepted pending a volunteer committed to its implementation label Aug 29, 2024
@arthanson arthanson self-assigned this Aug 29, 2024
@arthanson arthanson added the status: accepted This issue has been accepted for implementation label Aug 29, 2024
@arthanson arthanson mentioned this issue Aug 29, 2024
Merged
@jeremystretch jeremystretch mentioned this issue Sep 3, 2024
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@arthanson arthanson

Labels
beta Concerns a bug/feature in a beta release 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

No branches or pull requests
2 participants
@arthanson @jeremystretch