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
The root issue here is that NetBox's Location model evaluates the instance's primary key when determining whether the object is being created or updated in the database. Normally this is fine, however because we're populating a record (from a branch) with a predetermined primary key, this incorrect triggers MPTT to query for child locations.
I've opened NetBox bug #17577 to address this upstream, for all affected models.
Plugin Version
0.5.0
NetBox Version
4.1.1
Python Version
3.12
Steps to Reproduce
Expected Behavior
Merge to be successful.
Observed Behavior
Branch merge job shows the following:
{
"log": [
"Merging branch LOCTEST (branch_qv0723dh)",
"Found 2 changes to merge",
"Setting branch status to merging",
"Applying change DCIM | location TEST1 created by admin using default",
"Creating location <DeserializedObject: dcim.Location(pk=7875)>",
"Applying change DCIM | location TEST2 created by admin using default",
"Creating location <DeserializedObject: dcim.Location(pk=7876)>",
"Cannot call get_descendants on unsaved Location instances"
]
}
The text was updated successfully, but these errors were encountered: