Removing an ip-address from an interface results in no change #4100

Closed
opened 2025-12-29 18:33:07 +01:00 by adam · 1 comment
Owner

Originally created by @heiko-ma on GitHub (Sep 15, 2020).

Originally assigned to: @jeremystretch on GitHub.

Environment

  • Python version: v3.6.8
  • NetBox version: v2.9.3

Steps to Reproduce

  1. Create a new VM, i.e. 'testvm' and assign it to a cluster
  2. Create a new interface, i.e. 'Ethernet0'
  3. Create a new ip-address and attach it to the previously created interface
  4. Try to remove the ip-address from the interface by removing the vm from the corresponding fields in the ip-address edit dialog

Expected Behavior

The ip-address is unlinked from the device and no relation to the vm is displayed

Observed Behavior

I get the tooltip that the ip-address has been modified but no change is visible and the address is still linked to the interface.

This behavior can also be observed when I try to remove the link from a existing device (not virtual machine) so i think this is a general issue.

I'd be happy to supply you with any additional information

Originally created by @heiko-ma on GitHub (Sep 15, 2020). Originally assigned to: @jeremystretch on GitHub. <!-- NOTE: IF YOUR ISSUE DOES NOT FOLLOW THIS TEMPLATE, IT WILL BE CLOSED. 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, and that any plugins have been disabled. --> ### Environment * Python version: v3.6.8 * NetBox version: v2.9.3 <!-- Describe in detail the exact steps that someone else can take to reproduce this bug using the current stable release of NetBox. Begin with the creation of any necessary database objects and call out every operation being performed explicitly. If reporting a bug in the REST API, be sure to reconstruct the raw HTTP request(s) being made: Don't rely on a client library such as pynetbox. --> ### Steps to Reproduce 1. Create a new VM, i.e. 'testvm' and assign it to a cluster 2. Create a new interface, i.e. 'Ethernet0' 3. Create a new ip-address and attach it to the previously created interface 4. Try to remove the ip-address from the interface by removing the vm from the corresponding fields in the ip-address edit dialog <!-- What did you expect to happen? --> ### Expected Behavior The ip-address is unlinked from the device and no relation to the vm is displayed <!-- What happened instead? --> ### Observed Behavior I get the tooltip that the ip-address has been modified but no change is visible and the address is still linked to the interface. This behavior can also be observed when I try to remove the link from a existing device (not virtual machine) so i think this is a general issue. I'd be happy to supply you with any additional information
adam added the type: bugstatus: accepted labels 2025-12-29 18:33:08 +01:00
adam closed this issue 2025-12-29 18:33:08 +01:00
Author
Owner

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

It seems that this has been fixed in the develop branch as part of the work on #5105.

@jeremystretch commented on GitHub (Sep 16, 2020): It seems that this has been fixed in the `develop` branch as part of the work on #5105.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/netbox#4100