Changing device when editing IP address doesn't reset interface field #4461

Closed
opened 2025-12-29 18:36:12 +01:00 by adam · 2 comments
Owner

Originally created by @Gelob on GitHub (Jan 12, 2021).

Environment

  • Python version: Python 3.6.8
  • NetBox version: 2.10.3

Steps to Reproduce

  1. Create two devices with the same interface names (may not be required)
  2. Assign an IP address to Device A
  3. Edit the IP address and under Interface Assignment change the Device it is assigned to Device B
  4. Click Update and get a Modified IP address modal but notice the assignment did not change to Device B.

Expected Behavior

I expected the IP address to now be assigned to Device B instead of A. However the interface field under Interface Assignment doesn't refresh/reset when I change the device so the assignment stayed with Device A.

Observed Behavior

The IP address assignment didn't change to Device B because the interface was still referencing device A

Originally created by @Gelob on GitHub (Jan 12, 2021). ### Environment * Python version: Python 3.6.8 * NetBox version: 2.10.3 ### Steps to Reproduce 1. Create two devices with the same interface names (may not be required) 2. Assign an IP address to Device A 3. Edit the IP address and under Interface Assignment change the Device it is assigned to Device B 3. Click Update and get a Modified IP address modal but notice the assignment did not change to Device B. <!-- What did you expect to happen? --> ### Expected Behavior I expected the IP address to now be assigned to Device B instead of A. However the interface field under Interface Assignment doesn't refresh/reset when I change the device so the assignment stayed with Device A. <!-- What happened instead? --> ### Observed Behavior The IP address assignment didn't change to Device B because the interface was still referencing device A
adam added the pending closure label 2025-12-29 18:36:12 +01:00
adam closed this issue 2025-12-29 18:36:13 +01:00
Author
Owner

@DanSheps commented on GitHub (Jan 13, 2021):

Thank you for opening a bug report. It seems that the described functionality is intended behavior. If you meant to open a feature request instead, please close this issue and open a new one using the feature request template. Otherwise, please revise your post above to elaborate on why you believe the observed behavior is flawed.

@DanSheps commented on GitHub (Jan 13, 2021): Thank you for opening a bug report. It seems that the described functionality is intended behavior. If you meant to open a feature request instead, please close this issue and open a new one using the [feature request template](https://github.com/netbox-community/netbox/issues/new?template=feature_request.md). Otherwise, please revise your post above to elaborate on why you believe the observed behavior is flawed.
Author
Owner

@stale[bot] commented on GitHub (Jan 30, 2021):

This issue has been automatically closed due to lack of activity. In an effort to reduce noise, please do not comment any further. Note that the core maintainers may elect to reopen this issue at a later date if deemed necessary.

@stale[bot] commented on GitHub (Jan 30, 2021): This issue has been automatically closed due to lack of activity. In an effort to reduce noise, please do not comment any further. Note that the core maintainers may elect to reopen this issue at a later date if deemed necessary.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/netbox#4461