starred/netbox
1
0
Fork 0
mirror of https://github.com/netbox-community/netbox.git synced 2026-01-11 21:10:29 +01:00
Code Issues 273 Packages Projects Releases 10 Wiki Activity

API filtering 'OR' logic not working for dcim/devices "mac_address #2714

New Issue
Closed
opened 2025-12-29 18:21:21 +01:00 by adam · 1 comment
adam commented 2025-12-29 18:21:21 +01:00
Owner
Copy Link

Originally created by @ajknv on GitHub (Jul 1, 2019).

Environment

  • Python version: 3.6.8
  • NetBox version: 2.6.0

Steps to Reproduce

  1. Issue an API query with filter parameters specifying two different mac_address values, for example:
    https://netbox/api/dcim/devices/?mac_address=02%3A46%3A8A%3ABD%3AF1%3A35&mac_address=AB%3A77%3A65%3A4D%3ACB%3A10

Expected Behavior

API will return the two devices that have associated interfaces with the corresponding MAC addresses. (In this observed repro, the interfaces are known to be associated with distinct devices.)

Observed Behavior

API returned only the device with an interface matching the final mac_address filter, in this case the device with an interface for AB:77:65:4D:CB:10

Originally created by @ajknv on GitHub (Jul 1, 2019). ### Environment * Python version: 3.6.8 * NetBox version: 2.6.0 ### Steps to Reproduce 1. Issue an API query with filter parameters specifying two different mac_address values, for example: https://netbox/api/dcim/devices/?mac_address=02%3A46%3A8A%3ABD%3AF1%3A35&mac_address=AB%3A77%3A65%3A4D%3ACB%3A10 ### Expected Behavior API will return the two devices that have associated interfaces with the corresponding MAC addresses. (In this observed repro, the interfaces are known to be associated with distinct devices.) ### Observed Behavior API returned only the device with an interface matching the final mac_address filter, in this case the device with an interface for AB:77:65:4D:CB:10
adam closed this issue 2025-12-29 18:21:21 +01:00
adam commented 2025-12-29 18:21:22 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Jul 1, 2019):

Don't need a separate issue for this. Please just update #3315.

@jeremystretch commented on GitHub (Jul 1, 2019): Don't need a separate issue for this. Please just update #3315.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
beta
breaking change
complexity: high
complexity: low
complexity: medium
needs milestone
netbox
pending closure
plugin candidate
pull-request
Mirrored from GitHub Pull Request
 severity: high
severity: low
severity: medium
status: accepted
status: backlog
status: blocked
status: duplicate
status: needs owner
status: needs triage
status: revisions needed
status: under review
topic: GraphQL
topic: Internationalization
topic: OpenAPI
topic: UI/UX
topic: cabling
topic: event rules
topic: htmx navigation
topic: industrialization
topic: migrations
topic: plugins
topic: scripts
topic: templating
topic: testing
type: bug
type: deprecation
type: documentation
type: feature
type: housekeeping
type: translation
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
adam
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/netbox#2714
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?