Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Closed
proudbro opened this issue Apr 2, 2021 · 2 comments
Closed
Assignees
Labels
status: accepted This issue has been accepted for implementation type: bug A confirmed report of unexpected behavior in the application

Comments

@proudbro
Copy link

proudbro commented Apr 2, 2021

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

@proudbro proudbro added the type: bug A confirmed report of unexpected behavior in the application label Apr 2, 2021
@jeremystretch jeremystretch added the status: accepted This issue has been accepted for implementation label Apr 7, 2021
@jeremystretch jeremystretch self-assigned this Apr 7, 2021
jeremystretch added a commit that referenced this issue Apr 8, 2021
@proudbro
Copy link
Author

@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
Copy link
Author

proudbro commented Apr 16, 2021

I've created the new one

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Jul 16, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
status: accepted This issue has been accepted for implementation type: bug A confirmed report of unexpected behavior in the application
Projects
None yet
Development

No branches or pull requests

2 participants