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] Only one primary IP is shown when querying #18329

Closed
freym opened this issue Jan 7, 2025 · 2 comments · Fixed by #18345
Closed

[GraphQL] Only one primary IP is shown when querying #18329

freym opened this issue Jan 7, 2025 · 2 comments · Fixed by #18345
Assignees
Labels
severity: medium Results in substantial degraded or broken functionality for specfic workflows status: accepted This issue has been accepted for implementation type: bug A confirmed report of unexpected behavior in the application

Comments

@freym
Copy link

freym commented Jan 7, 2025

Deployment Type

Self-hosted

Triage priority

N/A

NetBox Version

v4.2.0

Python Version

3.12

Steps to Reproduce

  1. Create multiple Devices and assign different IPs to this devices.
  2. Mark these IPs as primary for the device.
  3. Run this GraphQL query:
{
  device_list {
    primary_ip4 {
      id
      display
    }
  }
}

Expected Behavior

A list with all primary IPs should be displayed

Observed Behavior

Only the first primary IP is displayed. All other IPs are NULL.

Example:
IPs:

  • 192.168.1.1
  • 192.168.1.2
  • 192.168.1.3

Only 192.168.1.1 is displayed, when you unmark this IP, 192.168.1.2 is displayed when running the query.

@freym freym added status: needs triage This issue is awaiting triage by a maintainer type: bug A confirmed report of unexpected behavior in the application labels Jan 7, 2025
@jeremystretch jeremystretch added status: needs owner This issue is tentatively accepted pending a volunteer committed to its implementation severity: medium Results in substantial degraded or broken functionality for specfic workflows and removed status: needs triage This issue is awaiting triage by a maintainer labels Jan 7, 2025
@freym
Copy link
Author

freym commented Jan 8, 2025

I had some time to take a closer look. This behavior has been occurring since v4.1.11.
There strawberry-graphql and strawberry-graphql-django packages were updated in v4.1.11. Is it possibly related to this?

@jeremystretch
Copy link
Member

There strawberry-graphql and strawberry-graphql-django packages were updated in v4.1.11. Is it possibly related to this?

Sure looks like it. I can confirm that the bug not reproducible with strawberry-graphql-django v0.52.0 installed. It appears that something broke in the v0.52.1 release.

I'm going to pin NetBox to v0.52.0 for now. This will likely need to be pursued upstream.

Thanks for digging into this @freym!

@jeremystretch jeremystretch added status: accepted This issue has been accepted for implementation and removed status: needs owner This issue is tentatively accepted pending a volunteer committed to its implementation labels Jan 8, 2025
@jeremystretch jeremystretch self-assigned this Jan 8, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
severity: medium Results in substantial degraded or broken functionality for specfic workflows status: accepted This issue has been accepted for implementation type: bug A confirmed report of unexpected behavior in the application
Projects
None yet
2 participants