API: Power Outlet Template Bug #3389

New Issue

adam · 2025-12-29T18:28:39+01:00

adam commented

2025-12-29 18:28:39 +01:00

Originally created by @minitriga on GitHub (Feb 24, 2020).

Originally assigned to: @jeremystretch on GitHub.

Environment

Python version: 3.7
NetBox version: 2.7.7

When creating a device type with the API adding a power outlet template to the device type produces errors.

Steps to Reproduce

Create Device Type
Add Power Port
Adding a power outlet template via API with the minimum amount of information required works (name, device_type) but this does not create a power outlet that is related to a power port.

{
  "device_type": 297,
  "name": "1"
}

Trying again on a new outlet number adding in the power_port information fails. Using the minimum amount of information required by the swagger API docs.

{
  "device_type": 297,
  "name": "2",
  "power_port": {
    "name": "Power Port",
    "device_type": {
      "model": "Test PDU",
      "slug": "test-pdu"
    }
  }
}

This produces the following error:

{
  "power_port": {
    "non_field_errors": [
      "The fields device_type, name must make a unique set."
    ]
  }
}

Expected Behavior

That a power outlet template is added to the database that is linked to a power port template for a device type.

Observed Behavior

Adding a power outlet fails as with the description following error:

{
  "power_port": {
    "non_field_errors": [
      "The fields device_type, name must make a unique set."
    ]
  }
}

I wonder if we could just use the ID of the power_port and make sure the power port is linked to the same device_type.

Thank you.

Originally created by @minitriga on GitHub (Feb 24, 2020). Originally assigned to: @jeremystretch on GitHub. ### Environment * Python version: 3.7 * NetBox version: 2.7.7 When creating a device type with the API adding a power outlet template to the device type produces errors.  ### Steps to Reproduce 1. Create Device Type 2. Add Power Port 3. Adding a power outlet template via API with the minimum amount of information required works (name, device_type) but this does not create a power outlet that is related to a power port. ``` { "device_type": 297, "name": "1" } ``` 4. Trying again on a new outlet number adding in the power_port information fails. Using the minimum amount of information required by the swagger API docs. ``` { "device_type": 297, "name": "2", "power_port": { "name": "Power Port", "device_type": { "model": "Test PDU", "slug": "test-pdu" } } } ``` This produces the following error: ``` { "power_port": { "non_field_errors": [ "The fields device_type, name must make a unique set." ] } } ```  ### Expected Behavior That a power outlet template is added to the database that is linked to a power port template for a device type.  ### Observed Behavior Adding a power outlet fails as with the description following error: ``` { "power_port": { "non_field_errors": [ "The fields device_type, name must make a unique set." ] } } ``` I wonder if we could just use the ID of the power_port and make sure the power port is linked to the same device_type. Thank you.

adam added the type: bug status: accepted labels 2025-12-29 18:28:39 +01:00

adam closed this issue

2025-12-29 18:28:39 +01:00

adam commented

2025-12-29 18:28:40 +01:00

@jeremystretch commented on GitHub (Feb 24, 2020):

{
  "device_type": 297,
  "name": "2",
  "power_port": {
    "name": "Power Port"
  }
}

The above should be all you need to create a new power outlet template on a device type. (Note that you could optionally use a dictionary specifying the device type manufacturer and model instead of its primary key if you prefer.) The commit pushed above should resolve this.

@jeremystretch commented on GitHub (Feb 24, 2020): ``` { "device_type": 297, "name": "2", "power_port": { "name": "Power Port" } } ``` The above should be all you need to create a new power outlet template on a device type. (Note that you could optionally use a dictionary specifying the device type manufacturer and model instead of its primary key if you prefer.) The commit pushed above should resolve this.

Sign in to join this conversation.

Branches Tags

main

update-changelog-comments-docs

feature-removal-issue-type

20911-dropdown

20239-plugin-menu-classes-mutable-state

21097-graphql-id-lookups

feature

fix_module_substitution

20923-dcim-templates

20044-elevation-stuck-lightmode

feature-ip-prefix-link

v4.5-beta1-release

20068-import-moduletype-attrs

20766-fix-german-translation-code-literals

20378-del-script

7604-filter-modifiers-v3

circuit-swap

12318-case-insensitive-uniqueness

20637-improve-device-q-filter

20660-script-load

19724-graphql

20614-update-ruff

14884-script

02496-max-page

19720-macaddress-interface-generic-relation

19408-circuit-terminations-export-templates

20203-openapi-check

fix-19669-api-image-download

7604-filter-modifiers

19275-fixes-interface-bulk-edit

fix-17794-get_field_value_return_list

11507-show-aggregate-and-rir-on-api

9583-add_column_specific_search_field_to_tables

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: starred/netbox#3389