GraphQL: - GraphQL not showing ALL connected cables #10800

New Issue

adam · 2025-12-29T21:36:03+01:00

adam commented

2025-12-29 21:36:03 +01:00

Originally created by @cruse1977 on GitHub (Feb 24, 2025).

Deployment Type

NetBox Cloud

NetBox Version

v4.2.4

Python Version

3.10

Steps to Reproduce

I've use demo.netbox.dev as an example however this is fairly easy to replicate in any instance:

create a device with some interfaces
connect a cable between 2 of the interfaces on the same device (note: where you connect the cables is irrelevant, this is just for speed).
Run the following graphql query replacing "device_name" with the name of the device to show interfaces and cables from a specific device

{
  device_list(filters: {name: {in_list: ["device name"]}}) {
    id
    name
    platform {
      slug
    }
    site {
      slug
    }
    interfaces {
      name
      cable {
        id
      }
    }
  }
}

this can be replicated on demo.netbox.dev using dmi01-buffalo-sw01 and creating a cable between Gi1/0/3 and Gi1/0/4 as an example.

Expected Behavior

Cables connected to interfaces are shown.

Observed Behavior

Only certain (older) cables are shown.

Example from demo.netbox.dev - whereas I have connected a cable between ports Gi0/0/3 and Gi0/0/4 of dmi-buffalo-sw01 as per the above.

However graphQL does not reflect this:

NOTE: API data returns correct results - this is specific to graphql.

Originally created by @cruse1977 on GitHub (Feb 24, 2025). ### Deployment Type NetBox Cloud ### NetBox Version v4.2.4 ### Python Version 3.10 ### Steps to Reproduce I've use demo.netbox.dev as an example however this is fairly easy to replicate in any instance: 1. create a device with some interfaces 2. connect a cable between 2 of the interfaces on the same device (note: where you connect the cables is irrelevant, this is just for speed). 3. Run the following graphql query replacing "device_name" with the name of the device to show interfaces and cables from a specific device ``` { device_list(filters: {name: {in_list: ["device name"]}}) { id name platform { slug } site { slug } interfaces { name cable { id } } } } ``` this can be replicated on demo.netbox.dev using dmi01-buffalo-sw01 and creating a cable between Gi1/0/3 and Gi1/0/4 as an example. ### Expected Behavior Cables connected to interfaces are shown. ### Observed Behavior Only certain (older) cables are shown. Example from demo.netbox.dev - whereas I have connected a cable between ports Gi0/0/3 and Gi0/0/4 of dmi-buffalo-sw01 as per the above. <img width="1550" alt="Image" src="https://github.com/user-attachments/assets/7daec71f-9c6f-4de8-bb35-737eebed8c27" /> However graphQL does not reflect this: <img width="1813" alt="Image" src="https://github.com/user-attachments/assets/93fe1db8-56c4-45f0-8a8e-9d871f80a6a0" /> NOTE: API data returns correct results - this is specific to graphql.

adam added the type: bug topic: GraphQL severity: low labels 2025-12-29 21:36:03 +01:00

adam closed this issue

2025-12-29 21:36:03 +01:00

adam commented

2025-12-29 21:36:04 +01:00

@jnovinger commented on GitHub (Mar 27, 2025):

@cruse1977 , I can't reproduce this anymore, either locally or on demo.netbox.dev. I've also not been able to track down when this might have been fixed. 😕

Can you confirm it's still happening for you?

@jnovinger commented on GitHub (Mar 27, 2025): @cruse1977 , I can't reproduce this anymore, either locally or on demo.netbox.dev. I've also not been able to track down when this might have been fixed. 😕 Can you confirm it's still happening for you? ![Image](https://github.com/user-attachments/assets/e9c6fe82-3fe3-45f1-aa82-fd35c6f92c35)

adam commented

2025-12-29 21:36:04 +01:00

@arthanson commented on GitHub (Apr 22, 2025):

This looks like it was fixed, no longer reproducible. Closing. @cruse1977 please re-open if you find a scenario where it is appearing but this reproduction seems fixed.

@arthanson commented on GitHub (Apr 22, 2025): This looks like it was fixed, no longer reproducible. Closing. @cruse1977 please re-open if you find a scenario where it is appearing but this reproduction seems fixed.

Sign in to join this conversation.

Branches Tags

main

update-changelog-comments-docs

feature-removal-issue-type

20911-dropdown

20239-plugin-menu-classes-mutable-state

21097-graphql-id-lookups

feature

fix_module_substitution

20923-dcim-templates

20044-elevation-stuck-lightmode

feature-ip-prefix-link

v4.5-beta1-release

20068-import-moduletype-attrs

20766-fix-german-translation-code-literals

20378-del-script

7604-filter-modifiers-v3

circuit-swap

12318-case-insensitive-uniqueness

20637-improve-device-q-filter

20660-script-load

19724-graphql

20614-update-ruff

14884-script

02496-max-page

19720-macaddress-interface-generic-relation

19408-circuit-terminations-export-templates

20203-openapi-check

fix-19669-api-image-download

7604-filter-modifiers

19275-fixes-interface-bulk-edit

fix-17794-get_field_value_return_list

11507-show-aggregate-and-rir-on-api

9583-add_column_specific_search_field_to_tables

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: starred/netbox#10800