REST API: GET /api/dcim/interface-connections/ doesn't show connections #4719

Closed
opened 2025-12-29 19:19:50 +01:00 by adam · 2 comments
Owner

Originally created by @proudbro on GitHub (Apr 2, 2021).

Originally assigned to: @jeremystretch on GitHub.

NetBox version

v2.10.8

Python version

3.6

Steps to Reproduce

  1. Create test device "TEST" with interfaces components
  2. Create cable connections for interfaces of test device with any other devices
  3. Try to GET <your.netbox.url>/api/dcim/interface-connections/?device=TEST OR GET <your.netbox.url>/api/dcim/interface-connections/?device_id=<id>

Expected Behavior

The list of connections of our TEST device with connected devices

Observed Behavior

Empty list of connections

HTTP 200 OK
Allow: GET, HEAD, OPTIONS
Content-Type: application/json
Vary: Accept

{
    "count": 0,
    "next": null,
    "previous": null,
    "results": []
}

This worked for sure in Netbox v2.6.6

Originally created by @proudbro on GitHub (Apr 2, 2021). Originally assigned to: @jeremystretch on GitHub. ### NetBox version v2.10.8 ### Python version 3.6 ### Steps to Reproduce 1. Create test device "TEST" with interfaces components 2. Create cable connections for interfaces of test device with any other devices 3. Try to` GET <your.netbox.url>/api/dcim/interface-connections/?device=TEST` OR `GET <your.netbox.url>/api/dcim/interface-connections/?device_id=<id>` ### Expected Behavior The list of connections of our TEST device with connected devices ### Observed Behavior Empty list of connections ``` HTTP 200 OK Allow: GET, HEAD, OPTIONS Content-Type: application/json Vary: Accept { "count": 0, "next": null, "previous": null, "results": [] } ``` This worked for sure in Netbox v2.6.6
adam added the type: bugstatus: accepted labels 2025-12-29 19:19:50 +01:00
adam closed this issue 2025-12-29 19:19:50 +01:00
Author
Owner

@proudbro commented on GitHub (Apr 14, 2021):

@jeremystretch , I still see the same behavior as before updating v2.10.9.
Try to GET interface connections and I get an empty list
GET /api/dcim/interface-connections/?device=<DEVICE_NAME> OR GET /api/dcim/interface-connections/?device_id=<DEVICE_ID>

HTTP 200 OK
Allow: GET, HEAD, OPTIONS
Content-Type: application/json
Vary: Accept

{
    "count": 0,
    "next": null,
    "previous": null,
    "results": []
}

Should I open a new issue?

@proudbro commented on GitHub (Apr 14, 2021): @jeremystretch , I still see the same behavior as before updating v2.10.9. Try to GET interface connections and I get an empty list `GET /api/dcim/interface-connections/?device=<DEVICE_NAME>` OR `GET /api/dcim/interface-connections/?device_id=<DEVICE_ID>` ``` HTTP 200 OK Allow: GET, HEAD, OPTIONS Content-Type: application/json Vary: Accept { "count": 0, "next": null, "previous": null, "results": [] } ``` Should I open a new issue?
Author
Owner

@proudbro commented on GitHub (Apr 16, 2021):

I've created the new one

@proudbro commented on GitHub (Apr 16, 2021): I've created the [new one](https://github.com/netbox-community/netbox/issues/6182)
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/netbox#4719