-
Notifications
You must be signed in to change notification settings - Fork 2.9k
Closed
Labels
status: acceptedThis issue has been accepted for implementationThis issue has been accepted for implementationtype: bugA confirmed report of unexpected behavior in the applicationA confirmed report of unexpected behavior in the application
Description
NetBox version
v3.3.5
Python version
3.10
Steps to Reproduce
- goto an ip address with an existing assignment, eg https://demo.netbox.dev/ipam/ip-addresses/186/
- edit the ip address, change the vm or device assignment, eg from vm1 to vm2.
- Notice that interface field below still says eth0
(its not obvious but that eth0 field is still set to eth0 on vm1, not eth0 on vm2 which is selected above) - user saves form, result is accepted. however interface assignment is still set to vm1 - eth0.
Expected Behavior
I would expect that at step 2 once the device or vm relationship was changed that the interfaces field would empty out
OR
that during the save process data validation would fail and tell the user that the device / virtual machine assignment + interface are not part of the same device.
OR
maybe the interface assignment (eth0) should also have the vm or device name listed after it? making it obvious that the field above didnt change anything and is just a filter?
Observed Behavior
assignment does not change in netbox. user gets no warning that there was a conflict or no change made
Metadata
Metadata
Assignees
Labels
status: acceptedThis issue has been accepted for implementationThis issue has been accepted for implementationtype: bugA confirmed report of unexpected behavior in the applicationA confirmed report of unexpected behavior in the application