starred/netbox
1
0
Fork 0
mirror of https://github.com/netbox-community/netbox.git synced 2026-01-14 06:13:32 +01:00
Code Issues 273 Packages Projects Releases 10 Wiki Activity

Server error when viewing cascaded PDUs #2692

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

Originally created by @sleeplessnight2 on GitHub (Jun 23, 2019).

Environment

  • Python version: 3.6.7-1~18.04
  • NetBox version: 2.6.0

Steps to Reproduce

1.Just open a previous cable Power port connected Device
2.
3.

Generate a Server Error.

The complete exception is provided below:

<class 'django.template.base.VariableDoesNotExist'>

Failed lookup for key [available_power] in <PowerOutlet: 6>

It seems, that something is forgotten on migrating to 2.6.0

I roll back to the older version (2.5.12), because i can't call some Devices in this Version.

Originally created by @sleeplessnight2 on GitHub (Jun 23, 2019). ### Environment * Python version: 3.6.7-1~18.04 * NetBox version: 2.6.0 ### Steps to Reproduce 1.Just open a previous cable Power port connected Device 2. 3. <!-- What happened instead? --> Generate a Server Error. The complete exception is provided below: > **<class 'django.template.base.VariableDoesNotExist'>** > > Failed lookup for key [available_power] in <PowerOutlet: 6> > It seems, that something is forgotten on migrating to 2.6.0 I roll back to the older version (2.5.12), because i can't call some Devices in this Version.
adam added the type: bugstatus: accepted labels 2025-12-29 18:21:09 +01:00
adam closed this issue 2025-12-29 18:21:09 +01:00
adam commented 2025-12-29 18:21:10 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Jun 24, 2019):

Please provide the exact steps someone can take to reproduce the problem.

@jeremystretch commented on GitHub (Jun 24, 2019): Please provide the exact steps someone can take to reproduce the problem.
adam commented 2025-12-29 18:21:10 +01:00
Author
Owner
Copy Link

@phurrelmann commented on GitHub (Jun 24, 2019):

This issue only pops up when one device has power ports and power outlets and is connected with its power port to another power outlet. The use case is to model cascaded power strips:
Strip A (1U) is connected to Feed A via its power port and has 7 power outlets. Strip B (1U) has 7 power outlets and is cascaded with Strip A (e.g. power outlet 7 of Strip A is connected the power port of Strip B).

Steps to Reproduce

  1. Update a pre Netbox 2.6 that has the described power connection configured
  2. Update to Netbox 2.6
  3. Try to edit/view the device that has the connected power-port

The following error is shown:

2019-06-24_09-24

@phurrelmann commented on GitHub (Jun 24, 2019): This issue only pops up when one device has power ports _and_ power outlets _and_ is connected with its power port to another power outlet. The use case is to model cascaded power strips: Strip A (1U) is connected to Feed A via its power port and has 7 power outlets. Strip B (1U) has 7 power outlets and is cascaded with Strip A (e.g. power outlet 7 of Strip A is connected the power port of Strip B). **Steps to Reproduce** 1. Update a pre Netbox 2.6 that has the described power connection configured 2. Update to Netbox 2.6 3. Try to edit/view the device that has the connected power-port The following error is shown: ![2019-06-24_09-24](https://user-images.githubusercontent.com/10113716/60023940-1e0e6a00-9697-11e9-8403-fb841ebe73bd.png)
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#2692
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?