Unable to assign existing IP address to VM interface #4052

New Issue

adam · 2025-12-29T18:32:51+01:00

adam commented

2025-12-29 18:32:51 +01:00

Originally created by @abrahamvegh on GitHub (Sep 1, 2020).

Originally assigned to: @jeremystretch on GitHub.

Environment

Python version: 3.7.3
NetBox version: 2.9.2

Steps to Reproduce

Create a VM with an interface
Click the ‘+’ button on the interface to add an IP address
Click the ‘Assign IP’ tab

Expected Behavior

The ‘Select IP Address’ form appears and functions correctly, as it does for non-VM interfaces.

Observed Behavior

The page redirects to /ipam/ip-addresses/add/, with no query parameters.

Notes

This is the same issue as #5041, but as it seems I cannot re-open that issue, here’s a new one. 😅

Originally created by @abrahamvegh on GitHub (Sep 1, 2020). Originally assigned to: @jeremystretch on GitHub. ### Environment * Python version: 3.7.3 * NetBox version: 2.9.2 ### Steps to Reproduce 1. Create a VM with an interface 2. Click the ‘+’ button on the interface to add an IP address 3. Click the ‘Assign IP’ tab ### Expected Behavior The ‘Select IP Address’ form appears and functions correctly, as it does for non-VM interfaces. ### Observed Behavior The page redirects to `/ipam/ip-addresses/add/`, with no query parameters. ### Notes This is the same issue as #5041, but as it seems I cannot re-open that issue, here’s a new one. 😅

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

adam closed this issue

2025-12-29 18:32:51 +01:00

adam commented

2025-12-29 18:32:52 +01:00

@bartdebruijn commented on GitHub (Sep 1, 2020):

This also applies to regular devices, e.g. /ipam/ip-addresses/ doesn't seem to retrieve information.
You can add an IP to an interface on a device, but it won't show up here.

@bartdebruijn commented on GitHub (Sep 1, 2020): This also applies to regular devices, e.g. /ipam/ip-addresses/ doesn't seem to retrieve information. You can add an IP to an interface on a device, but it won't show up here.

adam commented

2025-12-29 18:32:52 +01:00

@bartdebruijn commented on GitHub (Sep 1, 2020):

Specifically, the "assigned*" fields from /api/ipam/ip-addresses/ are not displayed on screen:

  "assigned_object_type": "dcim.interface",
  "assigned_object_id": 1,
  "assigned_object": {
    "id": 1,
    "url": "http://127.0.0.1:8000/api/dcim/interfaces/1/",
    "device": {
      "id": 1,
      "url": "http://127.0.0.1:8000/api/dcim/devices/1/",
      "name": "switch1",
      "display_name": "switch1"
    },
    "name": "Vlan99",

@bartdebruijn commented on GitHub (Sep 1, 2020): Specifically, the "assigned*" fields from /api/ipam/ip-addresses/ are not displayed on screen: "assigned_object_type": "dcim.interface", "assigned_object_id": 1, "assigned_object": { "id": 1, "url": "http://127.0.0.1:8000/api/dcim/interfaces/1/", "device": { "id": 1, "url": "http://127.0.0.1:8000/api/dcim/devices/1/", "name": "switch1", "display_name": "switch1" }, "name": "Vlan99", <img width="931" alt="Screenshot 2020-09-01 at 16 00 56" src="https://user-images.githubusercontent.com/340639/91860771-5ed71b00-ec6c-11ea-8e9e-ad7c7b982f32.png">

adam commented

2025-12-29 18:32:52 +01:00

@abrahamvegh commented on GitHub (Sep 1, 2020):

@bartdebruijn Something seems to be very wrong here. I went looking at what you’re talking about (the maintainers will probably require you to open a separate issue for that), but I then bumped into #5085 — core functionality seems to be broken.

@abrahamvegh commented on GitHub (Sep 1, 2020): @bartdebruijn Something seems to be very wrong here. I went looking at what you’re talking about (the maintainers will probably require you to open a separate issue for that), but I then bumped into #5085 — core functionality seems to be broken.

adam commented

2025-12-29 18:32:52 +01:00

@jeremystretch commented on GitHub (Sep 1, 2020):

#5085 is unrelated to this issue.

The root problem stems from having to handle both interface and vmitnerface query parameters, as there are now two separate models for device and VM interfaces. However, given the limited and redundant functionality of the assignment view, it may be more prudent to simply remove it entirely: IP address assignment is arguably done more directly via the normal IP address edit view, as opposed to following a separate obscure workflow.

@jeremystretch commented on GitHub (Sep 1, 2020): #5085 is unrelated to this issue. The root problem stems from having to handle both `interface` and `vmitnerface` query parameters, as there are now two separate models for device and VM interfaces. However, given the limited and redundant functionality of the assignment view, it may be more prudent to simply remove it entirely: IP address assignment is arguably done more directly via the normal IP address edit view, as opposed to following a separate obscure workflow.

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