API endpoints missing for front/rear port cable traces #3761

Closed
opened 2025-12-29 18:31:06 +01:00 by adam · 0 comments
Owner

Originally created by @jeremystretch on GitHub (Jun 9, 2020).

Originally assigned to: @jeremystretch on GitHub.

Environment

  • Python version: 3.6.9
  • NetBox version: 2.8.5

Steps to Reproduce

  1. Create a device with at least one rear port and note the rear port's numeric ID
  2. Connect a cable between the rear port and a suitable far-end component
  3. GET /api/dcim/rear-ports/<id>/trace/

Expected Behavior

The API request should return a JSON representation of the cable trace, as it does with other components.

Observed Behavior

The request returns a 404 error. Both front and rear ports are affected.

Originally created by @jeremystretch on GitHub (Jun 9, 2020). Originally assigned to: @jeremystretch on GitHub. ### Environment * Python version: 3.6.9 * NetBox version: 2.8.5 ### Steps to Reproduce 1. Create a device with at least one rear port and note the rear port's numeric ID 2. Connect a cable between the rear port and a suitable far-end component 3. `GET /api/dcim/rear-ports/<id>/trace/` ### Expected Behavior The API request should return a JSON representation of the cable trace, as it does with other components. ### Observed Behavior The request returns a 404 error. Both front and rear ports are affected.
adam added the type: bugstatus: accepted labels 2025-12-29 18:31:06 +01:00
adam closed this issue 2025-12-29 18:31:06 +01:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/netbox#3761