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 error "Expected value of type 'InterfaceType' but got: <VMInterface instance>." when querying interfaces from a VM #16124

Closed
derdeagle opened this issue May 14, 2024 · 1 comment · Fixed by #16126
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

@derdeagle
Copy link

derdeagle commented May 14, 2024

Deployment Type

Self-hosted

NetBox Version

v4.0.1

Python Version

3.11

Steps to Reproduce

  1. execute the following GraphQL query
{
  virtual_machine_list {
    name
    interfaces {
      mode
    }
  }
}

Expected Behavior

A valid resultset should be returned.

Observed Behavior

The following result containing the error message "Expected value of type 'InterfaceType' but got: ." is being returned.

{
  "data": null,
  "errors": [
    {
      "message": "Expected value of type 'InterfaceType' but got: <VMInterface instance>.",
      "locations": [
        {
          "line": 4,
          "column": 5
        }
      ],
      "path": [
        "virtual_machine_list",
        0,
        "interfaces",
        0
      ]
    }
  ]
}

This can be reproduced on the NetBox demo page.

I updated from 3.7.8 (where it worked as intended) to 4.0.1.

@derdeagle derdeagle added status: needs triage This issue is awaiting triage by a maintainer type: bug A confirmed report of unexpected behavior in the application labels May 14, 2024
@jeremystretch jeremystretch added status: accepted This issue has been accepted for 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 May 14, 2024
@derdeagle
Copy link
Author

@jeremystretch Thank you very much for your quick reaction.

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