Error when assigning a VM interface to a parent interface #5044

New Issue

adam · 2025-12-29T19:23:29+01:00

adam commented

2025-12-29 19:23:29 +01:00

Originally created by @jeremystretch on GitHub (Jul 7, 2021).

Originally assigned to: @jeremystretch on GitHub.

NetBox version

v2.11.8

Python version

3.7

Steps to Reproduce

Create a new VM and note its ID (ex: 123)
Create interface eth0 on the VM and note its ID (ex: 456)
Make a REST API call to create a second interface on the VM, assigning the first interface as its parent:

curl -X POST \
-H "Authorization: Token $TOKEN" \
-H "Content-Type: application/json" \
-H "Accept: application/json; indent=4" \
http://netbox/api/virtualization/interfaces/ \
--data '{"virtual_machine": 123, "name": "new", "parent": 456}'

This was originally reported under #6709.

Expected Behavior

The second interface should be created successfully, with the first interface assigned as its parent.

Observed Behavior

One of two things might happen, depending on how many device interfaces have been created:

A ValueError exception is raised.
The following error is returned:

{
    "parent": [
        "Related object not found using the provided numeric ID: 456"
    ]
}

This is due a bug in the definition of NestedVirtualMachineSerializer, which incorrectly references the dcim.Interface model.

Originally created by @jeremystretch on GitHub (Jul 7, 2021). Originally assigned to: @jeremystretch on GitHub. ### NetBox version v2.11.8 ### Python version 3.7 ### Steps to Reproduce 1. Create a new VM and note its ID (ex: 123) 2. Create interface eth0 on the VM and note its ID (ex: 456) 3. Make a REST API call to create a second interface on the VM, assigning the first interface as its parent: ``` curl -X POST \ -H "Authorization: Token $TOKEN" \ -H "Content-Type: application/json" \ -H "Accept: application/json; indent=4" \ http://netbox/api/virtualization/interfaces/ \ --data '{"virtual_machine": 123, "name": "new", "parent": 456}' ``` This was originally reported under #6709. ### Expected Behavior The second interface should be created successfully, with the first interface assigned as its parent. ### Observed Behavior One of two things might happen, depending on how many _device_ interfaces have been created: 1. A ValueError exception is raised. 2. The following error is returned: ``` { "parent": [ "Related object not found using the provided numeric ID: 456" ] } ``` This is due a bug in the definition of NestedVirtualMachineSerializer, which incorrectly references the dcim.Interface model.

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

adam closed this issue

2025-12-29 19:23:30 +01:00

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