You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I noticed a behavior change between 2.3.0 and the demo version 2.4.0b1 but I could not locate the appropriate commit.
1.Create a prefix without parents.(Easier done in a new namespace)
2.Create one or many ip addresses under this prefix
3.rename the prefix.
Expected Behavior
The ip addresses belonging to the original prefix should become orphan or the model should prevent the prefix from being renamed.
Since the model does not allow an ip to be orphan. I would expect renaming the prefix impossible until the user renames all IP addresses...?
Environment
Steps to Reproduce
I noticed a behavior change between 2.3.0 and the demo version 2.4.0b1 but I could not locate the appropriate commit.
1.Create a prefix without parents.(Easier done in a new namespace)
2.Create one or many ip addresses under this prefix
3.rename the prefix.
Expected Behavior
The ip addresses belonging to the original prefix should become orphan or the model should prevent the prefix from being renamed.
Since the model does not allow an ip to be orphan. I would expect renaming the prefix impossible until the user renames all IP addresses...?
Observed Behavior
The prefix shown in the GUI has no ip addresses which is expected. However the Ip addresses still have a parent connection with the renamed prefix.
See :
https://next.demo.nautobot.com/ipam/ip-addresses/9c84aa9c-f892-4138-8cb8-4854009c8e90/?tab=main
IP address 192.168.1.1/24 has 192.168.42.0/24 as parent.
The text was updated successfully, but these errors were encountered: