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

API filtering with 'status__n' on Object (prefix, device, ..) NOT Working #17721

Closed
Etibru opened this issue Oct 10, 2024 · 2 comments
Closed
Labels
status: duplicate This issue has already been raised type: bug A confirmed report of unexpected behavior in the application

Comments

@Etibru
Copy link

Etibru commented Oct 10, 2024

Deployment Type

Self-hosted

Triage priority

It's an important regretion

NetBox Version

v4.1.2

Python Version

3.12

Steps to Reproduce

  1. Call the API on :

The problem seems to be on all API status__n object filters, maybe even others.

Expected Behavior

This should return the list filtered by status

Observed Behavior

{
    "status__n": [
        "Select a valid choice. container is not one of the available choices."
    ]
}
{
  "status__n": [
    "Select a valid choice. planned is not one of the available choices."
  ]
}

@Etibru Etibru added status: needs triage This issue is awaiting triage by a maintainer type: bug A confirmed report of unexpected behavior in the application labels Oct 10, 2024
@Etibru Etibru changed the title API filleting with status__n in prefix NOT Working API filleting with 'status__n' on Object NOT Working Oct 10, 2024
@Etibru Etibru changed the title API filleting with 'status__n' on Object NOT Working API filleting with 'status__n' on Object (prefix, device, ..) NOT Working Oct 10, 2024
@sleepinggenius2
Copy link
Contributor

This was already fixed in #17670, which should be included in the 4.1.4 release.

@jeremystretch jeremystretch changed the title API filleting with 'status__n' on Object (prefix, device, ..) NOT Working API filtering with 'status__n' on Object (prefix, device, ..) NOT Working Oct 10, 2024
@jeremystretch
Copy link
Member

Going to close this as likely a duplicate of #17663. It can be re-opened if it's determined that the issue was not fixed in v4.1.4.

@jeremystretch jeremystretch closed this as not planned Won't fix, can't repro, duplicate, stale Oct 10, 2024
@jeremystretch jeremystretch added status: duplicate This issue has already been raised and removed status: needs triage This issue is awaiting triage by a maintainer labels Oct 10, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
status: duplicate This issue has already been raised type: bug A confirmed report of unexpected behavior in the application
Projects
None yet
Development

No branches or pull requests

3 participants