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

Small VM ressources display bugs #5283

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

Originally created by @EHRETic on GitHub (Sep 1, 2021).

NetBox version

v3.0.0

Python version

3.9

Steps to Reproduce

Enter information in VM hardware specs and go back to VM main page

Expected Behavior

  • VM vCPU should be displayed with an integer
  • Only one unit should be picked (but GB would be nice if memory size is a multiple of 1024)

Observed Behavior

I noticed when entering the different VM resources info that:

  • VM vCPU number is with 2 decimals, I don't think it is necessary
  • VM memory size is displayed with 2 units as I entered 2048 MB

image

Not something dramatic of course, but I noticed it, so I pass you the info! 😉

Originally created by @EHRETic on GitHub (Sep 1, 2021). ### NetBox version v3.0.0 ### Python version 3.9 ### Steps to Reproduce Enter information in VM hardware specs and go back to VM main page ### Expected Behavior - VM vCPU should be displayed with an integer - Only one unit should be picked (but GB would be nice if memory size is a multiple of 1024) ### Observed Behavior I noticed when entering the different VM resources info that: - VM vCPU number is with 2 decimals, I don't think it is necessary - VM memory size is displayed with 2 units as I entered 2048 MB ![image](https://user-images.githubusercontent.com/28634810/131651167-80c4fd3b-9b7b-4635-9823-60f569258d93.png) Not something dramatic of course, but I noticed it, so I pass you the info! 😉
adam added the type: bugstatus: duplicate labels 2025-12-29 19:26:11 +01:00
adam closed this issue 2025-12-29 19:26:11 +01:00
adam commented 2025-12-29 19:26:11 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Sep 1, 2021):

Thank you for submitting this issue, however it appears that this topic has already been raised. Please see issue #7083 for further discussion.

@jeremystretch commented on GitHub (Sep 1, 2021): Thank you for submitting this issue, however it appears that this topic has already been raised. Please see issue #7083 for further discussion.
adam commented 2025-12-29 19:26:11 +01:00
Author
Owner
Copy Link

@EHRETic commented on GitHub (Sep 1, 2021):

No problem, I didn't see it but if you can still transform CPU count to an integer... 😊

@EHRETic commented on GitHub (Sep 1, 2021): No problem, I didn't see it but if you can still transform CPU count to an integer... 😊
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#5283
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?