"Invalid data" error on certain nested API serializers #1899

New Issue

adam · 2025-12-29T17:20:12+01:00

adam commented

2025-12-29 17:20:12 +01:00

Originally created by @jeremystretch on GitHub (Aug 6, 2018).

Environment

Python version: 3.5.2
NetBox version: 2.4.0

Steps to Reproduce

This is an extension of the issue reported in #2299 during the v2.4 beta. Several nested API serializers have been identified as improperly handling posted data. Specifically, they expect a dictionary representation of an object rather than an integer (primary key). For example:

curl -X PATCH \
-H "Authorization: Token <TOKEN>" \
-H "Content-Type: application/json" \
-H "Accept: application/json; indent=4" \
http://localhost:8000/api/dcim/devices/<pk>/ \
--data '{"cluster": 123}'

The following models and fields have been identified as affected by this bug:

Device: cluster, primary_ip4, primary_ip6, virtual_chassis
VirtualMachine: primary_ip4, primary_ip6

Expected Behavior

The device should be assigned to the specified cluster.

Observed Behavior

The request yields the following validation error:

{
    "cluster": {
        "non_field_errors": [
            "Invalid data. Expected a dictionary, but got int."
        ]
    }
}

Originally created by @jeremystretch on GitHub (Aug 6, 2018). ### Environment * Python version: 3.5.2 * NetBox version: 2.4.0 ### Steps to Reproduce This is an extension of the issue reported in #2299 during the v2.4 beta. Several nested API serializers have been identified as improperly handling posted data. Specifically, they expect a dictionary representation of an object rather than an integer (primary key). For example: ``` curl -X PATCH \ -H "Authorization: Token <TOKEN>" \ -H "Content-Type: application/json" \ -H "Accept: application/json; indent=4" \ http://localhost:8000/api/dcim/devices/<pk>/ \ --data '{"cluster": 123}' ``` The following models and fields have been identified as affected by this bug: * Device: `cluster`, `primary_ip4`, `primary_ip6`, `virtual_chassis` * VirtualMachine: `primary_ip4`, `primary_ip6` ### Expected Behavior The device should be assigned to the specified cluster. ### Observed Behavior The request yields the following validation error: ``` { "cluster": { "non_field_errors": [ "Invalid data. Expected a dictionary, but got int." ] } } ```

adam added the type: bug status: accepted labels 2025-12-29 17:20:12 +01:00

adam closed this issue

2025-12-29 17:20:12 +01:00

adam referenced this issue

2025-12-29 20:47:42 +01:00

psycopg[binary,pool] breaks s390x deployments #9269

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#1899