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

Module type power ports should not be unique on same device #9209

New Issue
Closed
opened 2025-12-29 20:47:04 +01:00 by adam · 1 comment
adam commented 2025-12-29 20:47:04 +01:00
Owner
Copy Link

Originally created by @dejantep on GitHub (Feb 7, 2024).

Deployment Type

Self-hosted

NetBox Version

3.5.7

Python Version

3.8

Steps to Reproduce

  1. Create device with two module bays
  2. Create module type
  3. Add power port to module type and give it a name
  4. Install module in first bay
  5. Install same module in second bay

Expected Behavior

Device with module bays shouls be able to install same modules in different bays. Lets say line cards or mda etc
Power ports / connectors are the same

Observed Behavior

Error - Port name already exists on this device

Originally created by @dejantep on GitHub (Feb 7, 2024). ### Deployment Type Self-hosted ### NetBox Version 3.5.7 ### Python Version 3.8 ### Steps to Reproduce 1. Create device with two module bays 2. Create module type 3. Add power port to module type and give it a name 4. Install module in first bay 5. Install same module in second bay ### Expected Behavior Device with module bays shouls be able to install same modules in different bays. Lets say line cards or mda etc Power ports / connectors are the same ### Observed Behavior Error - Port name already exists on this device
adam closed this issue 2025-12-29 20:47:05 +01:00
adam commented 2025-12-29 20:47:05 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Feb 7, 2024):

This is not a bug. Uniqueness is enforced for power port names on a device, regardless of whether they belong to different modules.

@jeremystretch commented on GitHub (Feb 7, 2024): This is not a bug. Uniqueness is enforced for power port names on a device, regardless of whether they belong to different modules.
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#9209
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?