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

Modular PDU nested utilization/calculation does not work #4444

New Issue
Closed
opened 2025-12-29 18:36:03 +01:00 by adam · 1 comment
adam commented 2025-12-29 18:36:03 +01:00
Owner
Copy Link

Originally created by @fggec on GitHub (Jan 8, 2021).

Environment

  • Python version: 3.8.6
  • NetBox version: v2.9.8

Steps to Reproduce

  1. Create PDU parent device with some power outlets and assign a feed to the power port
  2. create PDU module as child device with some ports like C19 or something and connect it to one power outlet of the parent PDU
  3. connect an device with an allocated and maximum draw as known.

Expected Behavior

the draw from the power port of the module/child should be nested calculated to the parent device so that we could see the current utilization on the parent PDU

Observed Behavior

the utilization was not calculated by itself. We had to manually calculate the utilization and edit the current allocation of the module.

Originally created by @fggec on GitHub (Jan 8, 2021). ### Environment * Python version: 3.8.6 * NetBox version: v2.9.8 <!-- Describe in detail the exact steps that someone else can take to reproduce this bug using the current stable release of NetBox. 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 client library such as pynetbox. --> ### Steps to Reproduce 1. Create PDU parent device with some power outlets and assign a feed to the power port 2. create PDU module as child device with some ports like C19 or something and connect it to one power outlet of the parent PDU 3. connect an device with an allocated and maximum draw as known. ### Expected Behavior the draw from the power port of the module/child should be nested calculated to the parent device so that we could see the current utilization on the parent PDU ### Observed Behavior the utilization was not calculated by itself. We had to manually calculate the utilization and edit the current allocation of the module.
adam closed this issue 2025-12-29 18:36:03 +01:00
adam commented 2025-12-29 18:36:03 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Jan 8, 2021):

PDU modules should not be modeled as child devices. Child devices are fully autonomous entities (e.g. blade servers). You can use inventory items to represent modules within a PDU, but the power ports and outlets must be assigned to the device itself.

@jeremystretch commented on GitHub (Jan 8, 2021): PDU modules should not be modeled as child devices. Child devices are fully autonomous entities (e.g. blade servers). You can use inventory items to represent modules within a PDU, but the power ports and outlets must be assigned to the device itself.
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
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#4444
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?