starred/netbox
1
0
Fork 0
mirror of https://github.com/netbox-community/netbox.git synced 2026-01-13 13:53:31 +01:00
Code Issues 273 Packages Projects Releases 10 Wiki Activity

ipam/ip-addresses does not support filter by assigned_object #4151

New Issue
Closed
opened 2025-12-29 18:33:28 +01:00 by adam · 1 comment
adam commented 2025-12-29 18:33:28 +01:00
Owner
Copy Link

Originally created by @jameno123 on GitHub (Sep 29, 2020).

Environment

  • Python version: 3.6.9
  • NetBox version: 2.9.3

Steps to Reproduce

  1. fetch api results of "ipam/ip-addresses' with curl from https://netbox/api/ipam/ip-addresses/?assigned_object_type=virtualization.vminterface&assigned_object_id=123

Expected Behavior

Returns only the ip addresses assigned to that object (vminterface # 123) as was possible in netbox 2.8 using the interface_id= filter.

Observed Behavior

Returns all ip addresses in netbox as if no filter was supplied

Notes

Without being able to filter for ip addresses assigned to a specific interface we are unable to generate configurations for various systems/services that we now depend on netbox for. Please restore this functionality that was broken with the model change from interface to generic forgien key change or instruct me with a better way to obtain a list of ips attached to a specific network interface.

Originally created by @jameno123 on GitHub (Sep 29, 2020). <!-- NOTE: IF YOUR ISSUE DOES NOT FOLLOW THIS TEMPLATE, IT WILL BE CLOSED. This form is only for reproducible bugs. If you need assistance with NetBox installation, or if you have a general question, DO NOT open an issue. Instead, post to our mailing list: https://groups.google.com/forum/#!forum/netbox-discuss Please describe the environment in which you are running NetBox. Be sure that you are running an unmodified instance of the latest stable release before submitting a bug report, and that any plugins have been disabled. --> ### Environment * Python version: 3.6.9 * NetBox version: 2.9.3 <!-- Describe in detail the exact steps that someone else can take to reproduce this bug using the current stable release of NetBox. Begin with the creation of any necessary database objects and call out every operation being performed explicitly. If reporting a bug in the REST API, be sure to reconstruct the raw HTTP request(s) being made: Don't rely on a client library such as pynetbox. --> ### Steps to Reproduce 1. fetch api results of "ipam/ip-addresses' with curl from https://netbox/api/ipam/ip-addresses/?assigned_object_type=virtualization.vminterface&assigned_object_id=123 <!-- What did you expect to happen? --> ### Expected Behavior Returns only the ip addresses assigned to that object (vminterface # 123) as was possible in netbox 2.8 using the interface_id= filter. <!-- What happened instead? --> ### Observed Behavior Returns all ip addresses in netbox as if no filter was supplied ### Notes Without being able to filter for ip addresses assigned to a specific interface we are unable to generate configurations for various systems/services that we now depend on netbox for. Please restore this functionality that was broken with the model change from interface to generic forgien key change or instruct me with a better way to obtain a list of ips attached to a specific network interface.
adam closed this issue 2025-12-29 18:33:28 +01:00
adam commented 2025-12-29 18:33:28 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Sep 29, 2020):

assigned_object_type and assigned_object_id are not valid query parameters. You can use interface or interface_id to filter by assigned device interface, and vminterface or vminterface_id to filter by assigned VM interface. Please see the API documentation (available at /api/docs/) for the complete list of available filters.

@jeremystretch commented on GitHub (Sep 29, 2020): `assigned_object_type` and `assigned_object_id` are not valid query parameters. You can use `interface` or `interface_id` to filter by assigned device interface, and `vminterface` or `vminterface_id` to filter by assigned VM interface. Please see the API documentation (available at `/api/docs/`) for the complete list of available filters.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
beta
breaking change
complexity: high
complexity: low
complexity: medium
needs milestone
netbox
pending closure
plugin candidate
pull-request
Mirrored from GitHub Pull Request
 severity: high
severity: low
severity: medium
status: accepted
status: backlog
status: blocked
status: duplicate
status: needs owner
status: needs triage
status: revisions needed
status: under review
topic: GraphQL
topic: Internationalization
topic: OpenAPI
topic: UI/UX
topic: cabling
topic: event rules
topic: htmx navigation
topic: industrialization
topic: migrations
topic: plugins
topic: scripts
topic: templating
topic: testing
type: bug
type: deprecation
type: documentation
type: feature
type: housekeeping
type: translation
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
adam
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/netbox#4151
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?