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
It does look like the PUT/PATCH REST API allows assigned_object_type and assigned_object_id to be set as separate fields, and I don't see at a glance any logic in the model clean method that checks that either both are null or both are non-null, so it looks like this should be pretty easy to recreate intentionally.
Environment
Steps to Reproduce
Unclear, all changes to IP objects are done via API,
and I have no idea what exactly caused this to happen
Expected Behavior
Any IPAddress with assigned_object_type_id set should have an assigned_object
Observed Behavior
The text was updated successfully, but these errors were encountered: