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

Range-Lookup not working vor vc_position in GraphQL #11670

New Issue
Open
opened 2025-12-29 21:48:19 +01:00 by adam · 0 comments
adam commented 2025-12-29 21:48:19 +01:00
Owner
Copy Link

Originally created by @dxks on GitHub (Oct 2, 2025).

NetBox Edition

NetBox Community

NetBox Version

v4.4.2

Python Version

3.12

Steps to Reproduce

Send a simple query towards the graphql-endpoint:
query { device_list(filters:{vc_position:{range_lookup:{start:0, end:20}}}) { id name virtual_chassis { id name member_count } } }

Expected Behavior

As there is no longer a filter for Devices to check which one is member of a Virtual_chassis, nor the possibility to filter that virtual_chassis_id is not null we try to overcome this by filtering the vc_position that must be defined.

The result should be a list of devices that have a vc_position assigned and therefore belongs to a virtual_chassis.

Observed Behavior

The following error raised:
{ "data": null, "errors": [ { "message": "Field 'vc_position' expected a number but got [0, 20].", "locations": [ { "line": 2, "column": 3 } ], "path": [ "device_list" ] } ] }

the comparison lookup (even with ranges) and filter lookup works.

Originally created by @dxks on GitHub (Oct 2, 2025). ### NetBox Edition NetBox Community ### NetBox Version v4.4.2 ### Python Version 3.12 ### Steps to Reproduce Send a simple query towards the graphql-endpoint: `query { device_list(filters:{vc_position:{range_lookup:{start:0, end:20}}}) { id name virtual_chassis { id name member_count } } }` ### Expected Behavior As there is no longer a filter for Devices to check which one is member of a Virtual_chassis, nor the possibility to filter that virtual_chassis_id is not null we try to overcome this by filtering the vc_position that must be defined. The result should be a list of devices that have a vc_position assigned and therefore belongs to a virtual_chassis. ### Observed Behavior The following error raised: `{ "data": null, "errors": [ { "message": "Field 'vc_position' expected a number but got [0, 20].", "locations": [ { "line": 2, "column": 3 } ], "path": [ "device_list" ] } ] }` the comparison lookup (even with ranges) and filter lookup works.
adam added the type: bugstatus: needs ownernetboxtopic: GraphQLseverity: low labels 2025-12-29 21:48:19 +01:00
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 netbox severity: low status: needs owner topic: GraphQL 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#11670
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?