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

GraphQL interface_list filtering by type does not work #16378

Closed
dmulyalin opened this issue Jun 1, 2024 · 2 comments
Closed

GraphQL interface_list filtering by type does not work #16378

dmulyalin opened this issue Jun 1, 2024 · 2 comments
Labels
severity: low Does not significantly disrupt application functionality, or a workaround is available status: needs owner This issue is tentatively accepted pending a volunteer committed to its implementation type: bug A confirmed report of unexpected behavior in the application

Comments

@dmulyalin
Copy link

Deployment Type

Self-hosted

NetBox Version

v4.0.3

Python Version

3.10

Steps to Reproduce

  1. Create device in netbox (fceos4 in this example)
  2. Create interface of type LAG
  3. Create interface of any other non-lag type
  4. run query
{
  interface: interface_list(
    filters: {
      device: ["fceos4"], 
      type: {exact: "lag"}
    }
  ) {
    name
    type
    device {
      name
    }
  }
}

or this variant:

{
  interface: interface_list(
    filters: {
      device: ["fceos4"], 
      AND: {type: {exact: "lag"}}
    }
  ) {
    name
    type
    device {
      name
    }
  }
}

Expected Behavior

Only should return interface of type lag

Observed Behavior

Returns device interface of all types ignoring the filter.

@dmulyalin dmulyalin added status: needs triage This issue is awaiting triage by a maintainer type: bug A confirmed report of unexpected behavior in the application labels Jun 1, 2024
@jeremystretch
Copy link
Member

Confirmed on v4.0.3. Wonder if it's a similar issue to #16261.

@jeremystretch jeremystretch added status: needs owner This issue is tentatively accepted pending a volunteer committed to its implementation severity: low Does not significantly disrupt application functionality, or a workaround is available and removed status: needs triage This issue is awaiting triage by a maintainer labels Jun 3, 2024
@arthanson
Copy link
Collaborator

This is actually a dupe of #16024 closing this one

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Sep 3, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
severity: low Does not significantly disrupt application functionality, or a workaround is available status: needs owner This issue is tentatively accepted pending a volunteer committed to its implementation type: bug A confirmed report of unexpected behavior in the application
Projects
None yet
Development

No branches or pull requests

3 participants