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 with 'status__n' on Object (prefix, device, ..) NOT Working #10346

New Issue
Closed
opened 2025-12-29 21:30:20 +01:00 by adam · 2 comments
adam commented 2025-12-29 21:30:20 +01:00
Owner
Copy Link

Originally created by @Etibru on GitHub (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."
  ]
}
Originally created by @Etibru on GitHub (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 : - http://X.X.X.X/api/ipam/prefixes/?status__n=container - http://X.X.X.X/api/dcim/devices/?status__n=planned 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." ] } ```
adam added the type: bugstatus: duplicate labels 2025-12-29 21:30:20 +01:00
adam closed this issue 2025-12-29 21:30:20 +01:00
adam commented 2025-12-29 21:30:21 +01:00
Author
Owner
Copy Link

@sleepinggenius2 commented on GitHub (Oct 10, 2024):

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

@sleepinggenius2 commented on GitHub (Oct 10, 2024): This was already fixed in #17670, which should be included in the 4.1.4 release.
adam commented 2025-12-29 21:30:21 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Oct 10, 2024):

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 commented on GitHub (Oct 10, 2024): 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.
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 status: duplicate type: bug
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#10346
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?