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

Power Maximum draw/Allocated draw missing on Device Types #2770

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

Originally created by @KennethFoliJorgensen on GitHub (Aug 1, 2019).

Environment

  • Python version: 3.6.3
  • NetBox version: 2.6.1

Steps to Reproduce

  1. Create a new Device Type
  2. Add Component -> Power Port

Expected Behavior

that i am able on Power Port to add data to the power consumption fields maximum_draw and allocated_draw.

Observed Behavior

you are only able to add name

Originally created by @KennethFoliJorgensen on GitHub (Aug 1, 2019). <!-- NOTE: This form is only for reproducible bugs. If you need assistance with NetBox installation, or if you have a general question, DO NOT open an issue. Instead, post to our mailing list: https://groups.google.com/forum/#!forum/netbox-discuss Please describe the environment in which you are running NetBox. Be sure that you are running an unmodified instance of the latest stable release before submitting a bug report. --> ### Environment * Python version: 3.6.3 * NetBox version: 2.6.1 <!-- Describe in detail the exact steps that someone else can take to reproduce this bug using the current stable release of NetBox (or the current beta release where applicable). Begin with the creation of any necessary database objects and call out every operation being performed explicitly. If reporting a bug in the REST API, be sure to reconstruct the raw HTTP request(s) being made: Don't rely on a wrapper like pynetbox. --> ### Steps to Reproduce 1. Create a new Device Type 2. Add Component -> Power Port <!-- What did you expect to happen? --> ### Expected Behavior that i am able on Power Port to add data to the power consumption fields maximum_draw and allocated_draw. <!-- What happened instead? --> ### Observed Behavior you are only able to add name
adam added the type: bugstatus: accepted labels 2025-12-29 18:22:00 +01:00
adam closed this issue 2025-12-29 18:22:01 +01:00
adam commented 2025-12-29 18:22:01 +01:00
Author
Owner
Copy Link

@DanSheps commented on GitHub (Aug 2, 2019):

I can get behind this, most device types are all going to have a similar base power draw (Example, Cisco Cat 9300's, while it depends on the PSU, the PSU we use is always 1100W).

By contrast, we might want to look at removing "Power Feed" from Power Outlet, as most device types won't be connected to the same feed.

@DanSheps commented on GitHub (Aug 2, 2019): I can get behind this, most device types are all going to have a similar base power draw (Example, Cisco Cat 9300's, while it depends on the PSU, the PSU we use is always 1100W). By contrast, we might want to look at removing "Power Feed" from Power Outlet, as most device types won't be connected to the same feed.
adam commented 2025-12-29 18:22:01 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Aug 2, 2019):

These fields were added to the model originally, but were not added to the form.

@jeremystretch commented on GitHub (Aug 2, 2019): These fields were added to the model originally, but were not added to the form.
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: 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#2770
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?