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

Clusters Section - Incorrect Hardisk Display Size #10295

New Issue
Closed
opened 2025-12-29 21:29:32 +01:00 by adam · 2 comments
adam commented 2025-12-29 21:29:32 +01:00
Owner
Copy Link

Originally created by @Ant0ni00x on GitHub (Sep 26, 2024).

Deployment Type

Self-hosted

NetBox Version

v4.1.1

Python Version

3.12

Steps to Reproduce

After creating Cluster Groups, Cluster Types and a Cluster, then creating a Virtual Machine, you'll see that the disk size displayed on the cluster page is not formatted correctly.

For example, I created two VMs, with total disk space size of 258.3GB. However, on the Clusters page, where the "Allocated Resources" card displays the total disk size for the cluster, the displayed disk size is 258300GB.

Cluster-Display-Issue

VM-Disk-Sizing

Expected Behavior

Seems that this number should actually be 258.3GB if displaying in GB. If displaying the disk size in MB, I can then understand the reason for the formatting. The expected behavior is to have the same GB formatting for disk space on the Virtual Machine and the Cluster - "Allocated Resources" card.

Observed Behavior

On the Clusters page, where the "Allocated Resources" card displays the total disk size for the cluster, the displayed disk size is 258300GB.

Originally created by @Ant0ni00x on GitHub (Sep 26, 2024). ### Deployment Type Self-hosted ### NetBox Version v4.1.1 ### Python Version 3.12 ### Steps to Reproduce After creating Cluster Groups, Cluster Types and a Cluster, then creating a Virtual Machine, you'll see that the disk size displayed on the cluster page is not formatted correctly. For example, I created two VMs, with total disk space size of 258.3GB. However, on the Clusters page, where the "Allocated Resources" card displays the total disk size for the cluster, the displayed disk size is 258300GB. ![Cluster-Display-Issue](https://github.com/user-attachments/assets/64c32adf-e6de-42ac-9416-4f0d0737327f) ![VM-Disk-Sizing](https://github.com/user-attachments/assets/04e80659-b894-4019-85ee-991785d59ae3) ### Expected Behavior Seems that this number should actually be 258.3GB if displaying in GB. If displaying the disk size in MB, I can then understand the reason for the formatting. The expected behavior is to have the same GB formatting for disk space on the Virtual Machine and the Cluster - "Allocated Resources" card. ### Observed Behavior On the Clusters page, where the "Allocated Resources" card displays the total disk size for the cluster, the displayed disk size is 258300GB.
adam added the type: bugstatus: duplicate labels 2025-12-29 21:29:32 +01:00
adam closed this issue 2025-12-29 21:29:33 +01:00
adam commented 2025-12-29 21:29:33 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Sep 26, 2024):

This is a duplicate of #17604. Please remember to search open issues before creating a new one.

@jeremystretch commented on GitHub (Sep 26, 2024): This is a duplicate of #17604. Please remember to search open issues before creating a new one.
adam commented 2025-12-29 21:29:33 +01:00
Author
Owner
Copy Link

@Ant0ni00x commented on GitHub (Sep 28, 2024):

Apologies.I know you guys are busy and don’t need the extra noise of redundant comments! My eagerness to feel helpful preceded the need to be more thorough.I’ll be more diligent in my search efforts if I ever see anything of significance again.Kind RegardsOn Sep 26, 2024, at 7:48 AM, Jeremy Stretch @.***> wrote:
This is a duplicate of #17604. Please remember to search open issues before creating a new one.

—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: @.***>

@Ant0ni00x commented on GitHub (Sep 28, 2024): Apologies.I know you guys are busy and don’t need the extra noise of redundant comments! My eagerness to feel helpful preceded the need to be more thorough.I’ll be more diligent in my search efforts if I ever see anything of significance again.Kind RegardsOn Sep 26, 2024, at 7:48 AM, Jeremy Stretch ***@***.***> wrote: This is a duplicate of #17604. Please remember to search open issues before creating a new one. —Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: ***@***.***>
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#10295
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?