Search interfaces in hierarchical structured locations fails #5954

New Issue

adam · 2025-12-29T19:34:52+01:00

adam commented

2025-12-29 19:34:52 +01:00

Originally created by @baschdello on GitHub (Jan 17, 2022).

NetBox version

v3.1.5

Python version

3.9

Steps to Reproduce

Create a hierarchical location set like:
block2
| --- rackrow3
| --- rackrow4

Create some racks and assign them to location "row3" and "row4".

Add some devices with interfaces in those racks.

After that use the interface search from menu "Devices => Interfaces" and choose filteroption location: "block2"

Expected Behavior

Interfaces from devices out of parent location "block2" should be listed.

Observed Behavior

None of device interfaces are listed.

Note: this problem is only observed at interface search. If using the device search under menu "Devices => Devices" and choose the parent location "block2" as filteroption like above all devices are listed.

Originally created by @baschdello on GitHub (Jan 17, 2022). ### NetBox version v3.1.5 ### Python version 3.9 ### Steps to Reproduce Create a hierarchical location set like: block2 | --- rackrow3 | --- rackrow4 Create some racks and assign them to location "row3" and "row4". Add some devices with interfaces in those racks. After that use the interface search from menu "Devices => Interfaces" and choose filteroption location: "block2" ### Expected Behavior Interfaces from devices out of parent location "block2" should be listed. ### Observed Behavior None of device interfaces are listed. ------ Note: this problem is only observed at interface search. If using the device search under menu "Devices => Devices" and choose the parent location "block2" as filteroption like above all devices are listed.

adam closed this issue

2025-12-29 19:34:52 +01:00

adam commented

2025-12-29 19:34:53 +01:00

@jeremystretch commented on GitHub (Jan 17, 2022):

Just like the region, site group, and site fields, the location field is there only to filter the list of available devices. It does not filter interfaces directly.

If you'd like to propose enabling a location filter for interfaces, please open a feature request citing your use case.

@jeremystretch commented on GitHub (Jan 17, 2022): Just like the region, site group, and site fields, the location field is there only to filter the list of available devices. It does not filter interfaces directly. If you'd like to propose enabling a location filter for interfaces, please open a [feature request](https://github.com/netbox-community/netbox/issues/new?assignees=&labels=type%3A+feature&template=feature_request.yaml) citing your use case.

Sign in to join this conversation.

Branches Tags

main

update-changelog-comments-docs

feature-removal-issue-type

20911-dropdown

20239-plugin-menu-classes-mutable-state

21097-graphql-id-lookups

feature

fix_module_substitution

20923-dcim-templates

20044-elevation-stuck-lightmode

feature-ip-prefix-link

v4.5-beta1-release

20068-import-moduletype-attrs

20766-fix-german-translation-code-literals

20378-del-script

7604-filter-modifiers-v3

circuit-swap

12318-case-insensitive-uniqueness

20637-improve-device-q-filter

20660-script-load

19724-graphql

20614-update-ruff

14884-script

02496-max-page

19720-macaddress-interface-generic-relation

19408-circuit-terminations-export-templates

20203-openapi-check

fix-19669-api-image-download

7604-filter-modifiers

19275-fixes-interface-bulk-edit

fix-17794-get_field_value_return_list

11507-show-aggregate-and-rir-on-api

9583-add_column_specific_search_field_to_tables

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: starred/netbox#5954