Skip to content

Sort/Filter is broken for dynamic columns that are not json paths #16071

@richard-cox

Description

@richard-cox

Setup

  • Rancher version: 2.12.0

Describe the bug

  • When there's no custom column definitions the UI will create them from the schema
  • The location of the of the value for the column is specified in two format
    • JSON Path
      • $.metadata.fields[1] (scheduling.k8s.io.priorityclass)
      • $.metadata.labels.node["kubernetes.io/instance-type"]
    • Not json path
      • .spec.url (management.cattle.io.nodedriver)
  • The UI converts non json paths to json paths
    • .spec.url --> $.spec.url
  • This works for local filtering and sorting
  • This does not work for vai filtering and sorting
    • 422 column is invalid [$.spec.url]: supplied column is invalid

To Reproduce

  • local cluster --> More Resources --> Rancher --> NodeDrivers
  • sort by binary url

Result

  • sort not applied, http error

Expected Result

  • sort applied

Metadata

Metadata

Assignees

Type

No type

Projects

No projects

Relationships

None yet

Development

No branches or pull requests

Issue actions