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

Unable to assign interface to IP address via API #1889

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

Originally created by @explody on GitHub (Aug 2, 2018).

Environment

  • Python version: 3.6.5, 3.5.x
  • NetBox version: 2.4-beta1

Steps to Reproduce

Using the API, attempt to PUT or PATCH an existing IP address including an interface id.

postman CURL output. Both IP and iface ID #'s exist and are correct
curl -X PATCH \
  https://ourhost/api/ipam/ip-addresses/11111/ \
  -H 'authorization: Token XXXX' \
  -H 'cache-control: no-cache' \
  -H 'content-type: application/json' \
  -H 'postman-token: XXXX' \
  -d '{
    "interface": 2222
}'

Expected Behavior

The IP would now be assigned to the given interface.

Observed Behavior

From postman, the following error:

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

We additionally tried to pass interface data as a nested hash, but encountered a variety of other errors. It appears that the shown approach should work, so this may hint at the base problem.

Originally created by @explody on GitHub (Aug 2, 2018). <!-- NOTE: This form is only for reproducible bugs. If you need assistance with NetBox installation, or if you have a general question, DO NOT open an issue. Instead, post to our mailing list: https://groups.google.com/forum/#!forum/netbox-discuss Please describe the environment in which you are running NetBox. Be sure that you are running an unmodified instance of the latest stable release before submitting a bug report. --> ### Environment * Python version: 3.6.5, 3.5.x * NetBox version: 2.4-beta1 <!-- Describe in detail the steps that someone else can take to reproduce this bug using the current stable release of NetBox (or the current beta release where applicable). --> ### Steps to Reproduce Using the API, attempt to PUT or PATCH an existing IP address including an interface id. ``` postman CURL output. Both IP and iface ID #'s exist and are correct curl -X PATCH \ https://ourhost/api/ipam/ip-addresses/11111/ \ -H 'authorization: Token XXXX' \ -H 'cache-control: no-cache' \ -H 'content-type: application/json' \ -H 'postman-token: XXXX' \ -d '{ "interface": 2222 }' ``` <!-- What did you expect to happen? --> ### Expected Behavior The IP would now be assigned to the given interface. <!-- What happened instead? --> ### Observed Behavior From postman, the following error: ``` { "interface": { "non_field_errors": [ "Invalid data. Expected a dictionary, but got int." ] } } ``` We additionally tried to pass interface data as a nested hash, but encountered a variety of other errors. It appears that the shown approach should work, so this may hint at the base problem.
adam added the type: bugstatus: accepted labels 2025-12-29 17:20:05 +01:00
adam closed this issue 2025-12-29 17:20:06 +01:00
adam commented 2025-12-29 17:20:06 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Aug 3, 2018):

Fixed in #2300. Thanks @explody!

@jeremystretch commented on GitHub (Aug 3, 2018): Fixed in #2300. Thanks @explody!
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#1889
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?