GET request for interfaces with device and mac as parameters returns nothing #2699

Closed
opened 2025-12-29 18:21:11 +01:00 by adam · 4 comments
Owner

Originally created by @melslow on GitHub (Jun 27, 2019).

Environment

  • Python version: 3.6
  • NetBox version: 2.6

Steps to Reproduce

  1. Create a device and assign a interface
  2. Request the created interface from the API by doing a GET interfaces with device and mac as parameters.
    `http://0.0.0.0:32776/api/dcim/interfaces/?device=example_devicet&mac_address=00%3A56%3A50%3A6d%3A2d%3A5a

Expected Behavior

Return the object that was created at the start of this test.

Observed Behavior

The API returns an empty response
After a while it does return the correct object so this might have something to do with the new caching?

Originally created by @melslow on GitHub (Jun 27, 2019). <!-- NOTE: This form is only for reproducible bugs. If you need assistance with NetBox installation, or if you have a general question, DO NOT open an issue. Instead, post to our mailing list: https://groups.google.com/forum/#!forum/netbox-discuss Please describe the environment in which you are running NetBox. Be sure that you are running an unmodified instance of the latest stable release before submitting a bug report. --> ### Environment * Python version: 3.6 * NetBox version: 2.6 <!-- Describe in detail the exact steps that someone else can take to reproduce this bug using the current stable release of NetBox (or the current beta release where applicable). Begin with the creation of any necessary database objects and call out every operation being performed explicitly. If reporting a bug in the REST API, be sure to reconstruct the raw HTTP request(s) being made: Don't rely on a wrapper like pynetbox. --> ### Steps to Reproduce 1. Create a device and assign a interface 2. Request the created interface from the API by doing a GET interfaces with device and mac as parameters. `http://0.0.0.0:32776/api/dcim/interfaces/?device=example_devicet&mac_address=00%3A56%3A50%3A6d%3A2d%3A5a <!-- What did you expect to happen? --> ### Expected Behavior Return the object that was created at the start of this test. <!-- What happened instead? --> ### Observed Behavior The API returns an empty response After a while it does return the correct object so this might have something to do with the new caching?
adam closed this issue 2025-12-29 18:21:11 +01:00
Author
Owner

@melslow commented on GitHub (Jun 27, 2019):

After some testing i found out that this problem is likely caused by the new caching system.
With caching disabled the API functions as expected.

@melslow commented on GitHub (Jun 27, 2019): After some testing i found out that this problem is likely caused by the new caching system. With caching disabled the API functions as expected.
Author
Owner

@jeremystretch commented on GitHub (Jun 27, 2019):

Please indicate your Python version as required by the template.

@jeremystretch commented on GitHub (Jun 27, 2019): Please indicate your Python version as required by the template.
Author
Owner

@melslow commented on GitHub (Jun 27, 2019):

Please indicate your Python version as required by the template.

Sorry, fixed it

@melslow commented on GitHub (Jun 27, 2019): > Please indicate your Python version as required by the template. Sorry, fixed it
Author
Owner

@jeremystretch commented on GitHub (Aug 19, 2019):

Rolling this into #3428

@jeremystretch commented on GitHub (Aug 19, 2019): Rolling this into #3428
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/netbox#2699