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

[backport v2.9.next1] Server-side Pagination: Sorting: Cluster Dash: Newly created resource populates at bottom of list; sort order preference ignored #11503

Closed
github-actions bot opened this issue Jul 22, 2024 · 1 comment
Assignees
Labels
area/server-side-pagination kind/bug QA/dev-automation Issues that engineers have written automation around so QA doesn't have look at this QA/None
Milestone

Comments

@github-actions
Copy link
Contributor

This is a backport issue for #11498, automatically created via GitHub Actions workflow initiated by @richard-cox

Original issue body:

Setup

  • Rancher version: v2.9-head
  • Rancher UI Extensions:
  • Browser type & version:

Describe the bug
Newly created resource populates at the bottom of the resource list (config maps, secrets) when server-side pag is enabled; sorting preference is ignored.

To Reproduce

  1. go to Global settings > feature flags > enable ui-sql-cache
  2. go to Global settings > performance > enable `Server-sdie Pagination'
  3. go to cluster dash
  4. click ConfigMaps in side nav
  5. notice secrets list is sorted by name by default
  6. create config map
  7. notice newly created secret is not sorted correctly

Result
sort order is preference is ignored.

Expected Result
sort order is not ignored.

Screenshots
https://github.com/user-attachments/assets/c6df7482-1225-43bc-889e-7bb239633ed5

Additional context

@github-actions github-actions bot added kind/bug QA/dev-automation Issues that engineers have written automation around so QA doesn't have look at this QA/None labels Jul 22, 2024
@github-actions github-actions bot added this to the v2.9.next1 milestone Jul 22, 2024
@richard-cox
Copy link
Member

Gonna keep things neater and use backport label in upstream ticket. The backport version also might change

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/server-side-pagination kind/bug QA/dev-automation Issues that engineers have written automation around so QA doesn't have look at this QA/None
Projects
None yet
Development

No branches or pull requests

1 participant