Expecting response with filtered list of ip-addresses with specified assigned_object_type (as it was on version 3)
Observed Behavior
Regardless of the parameter value (dcim.interface/virtualization.vminterface/ipam.fhrpgroup) get a response:
"assigned_object_type": [
"Select a valid choice. That choice is not one of the available choices."
]
From the docs: "assigned_object_type - The content type of the assigned object, defined as <app>.<model>".
It is noticed that the parameter accepts numeric values of identifiers from api/extras/object-types for GET requests and filtering works. However, for POST it responds with "'assigned_object_type': ["Invalid value. Specify a content type as '.'."]" and working with values defined as <app>.<model>.
Initially the problem was noticed after the update from 3.7.1 to 4.0.8, however, the behavior is the same on a clean installation of 4.1.1.
@Konunacmep which previous version of NetBox were you seeing this working in? I tried with v3.7 and it is not returning the interfaces using this query (see screenshot).
Deployment Type
Self-hosted
NetBox Version
v4.1.1
Python Version
3.11
Steps to Reproduce
Сan be reproduced on the demo.
Expected Behavior
Expecting response with filtered list of ip-addresses with specified assigned_object_type (as it was on version 3)
Observed Behavior
Regardless of the parameter value (dcim.interface/virtualization.vminterface/ipam.fhrpgroup) get a response: "assigned_object_type": [ "Select a valid choice. That choice is not one of the available choices." ] From the docs: "assigned_object_type - The content type of the assigned object, defined as
<app>.<model>
".It is noticed that the parameter accepts numeric values of identifiers from api/extras/object-types for GET requests and filtering works. However, for POST it responds with "'assigned_object_type': ["Invalid value. Specify a content type as '.'."]" and working with values defined as
<app>.<model>
.Initially the problem was noticed after the update from 3.7.1 to 4.0.8, however, the behavior is the same on a clean installation of 4.1.1.