Front port templates: No results when rear_port_id filter is set #11919

New Issue

adam · 2025-12-29T21:51:30+01:00

adam commented

2025-12-29 21:51:30 +01:00

Originally created by @vo42 on GitHub (Dec 11, 2025).

Originally assigned to: @vo42 on GitHub.

NetBox Edition

NetBox Community

NetBox Version

4.4.8

Python Version

3.12

Steps to Reproduce

Install Netbox with a fresh db
Create a site, device role and a device type. Do NOT create any front port or rear port. No need to create any device.
On the device type (not on a device), click on Add Components, create one rear port and one front port (RearPortTemplate and FrontPortTemplate).
Using the REST API, list the Front Port Templates and check that there is exactly one result, connected to the Rear Port Template with id==1 :

$ curl -s -H "Authorization: Token $TOKEN" 'http://127.0.0.1:8000/api/dcim/front-port-templates/' | jq '.results[] | {id, display, rear_port}'
{
  "id": 1,
  "display": "front",
  "rear_port": {
    "id": 1,
    "url": "http://127.0.0.1:8000/api/dcim/rear-port-templates/1/",
    "display": "rear",
    "name": "rear",
    "description": ""
  }
}

Using the same API route, search for a Front Port Template connected to the Rear Port Template with id = 1 :

$ curl -s -H "Authorization: Token $TOKEN" 'http://127.0.0.1:8000/api/dcim/front-port-templates/?rear_port_id=1'

Expected Behavior

The API should return the same result found in Step 4.

Observed Behavior

{"rear_port_id":["Select a valid choice. 1 is not one of the available choices."]}

I suspect the issue is in class FrontPortTemplateFilterSet in netbox/dcim/filtersets.py: replacing queryset=RearPort.objects.all() by queryset=RearPortTemplate.objects.all() seems to fix the issue.
Note that in the feature branch, a front_port_id filter was added to RearPortTemplateFilterSet by 17d8f78ae3 that most likely has the same issue (missing Template in the queryset).

I can provide PR if requested.

Originally created by @vo42 on GitHub (Dec 11, 2025). Originally assigned to: @vo42 on GitHub. ### NetBox Edition NetBox Community ### NetBox Version 4.4.8 ### Python Version 3.12 ### Steps to Reproduce 1. Install Netbox with a fresh db 2. Create a site, device role and a device type. Do NOT create any front port or rear port. No need to create any device. 3. On the **device _type_** (not on a _device_), click on Add Components, create one rear port and one front port (RearPortTemplate and FrontPortTemplate). 4. Using the REST API, list the Front Port Templates and check that there is exactly one result, connected to the Rear Port Template with id==1 : ``` $ curl -s -H "Authorization: Token $TOKEN" 'http://127.0.0.1:8000/api/dcim/front-port-templates/' | jq '.results[] | {id, display, rear_port}' { "id": 1, "display": "front", "rear_port": { "id": 1, "url": "http://127.0.0.1:8000/api/dcim/rear-port-templates/1/", "display": "rear", "name": "rear", "description": "" } } ``` 5. Using the same API route, search for a Front Port Template connected to the Rear Port Template with id = 1 : ``` $ curl -s -H "Authorization: Token $TOKEN" 'http://127.0.0.1:8000/api/dcim/front-port-templates/?rear_port_id=1' ``` ### Expected Behavior The API should return the same result found in Step 4. ### Observed Behavior ``` {"rear_port_id":["Select a valid choice. 1 is not one of the available choices."]} ``` I suspect the issue is in `class FrontPortTemplateFilterSet` in `netbox/dcim/filtersets.py`: replacing `queryset=RearPort.objects.all()` by `queryset=RearPortTemplate.objects.all()` seems to fix the issue. Note that in the `feature` branch, a front_port_id filter was added to **Rear**PortTemplateFilterSet by 17d8f78ae305396202c45522299ac44adb61373b that most likely has the same issue (missing `Template` in the queryset). I can provide PR if requested.

adam added the type: bug status: accepted netbox severity: low labels 2025-12-29 21:51:30 +01:00

adam closed this issue

2025-12-29 21:51:30 +01:00

adam commented

2025-12-29 21:51:31 +01:00

@jnovinger commented on GitHub (Dec 15, 2025):

Looks like you're correct, @vo42. Assigned to you. Thanks!

@jnovinger commented on GitHub (Dec 15, 2025): Looks like you're correct, @vo42. Assigned to you. Thanks!

Sign in to join this conversation.

Branches Tags

main

21102-fix-graphiql-explorer

update-changelog-comments-docs

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#11919