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

Resources status are always Unknown when Server Side Pagination is enabled HA #12265

Closed
izaac opened this issue Oct 15, 2024 · 5 comments
Closed
Assignees
Milestone

Comments

@izaac
Copy link
Contributor

izaac commented Oct 15, 2024

Setup

  • Rancher version: HA v2.10-2e82262225844f52c3ef6d8a8f51b870e220ec91-head
  • Rancher UI Extensions: master 4e0aa07
  • Browser type & version:

Describe the bug
Clusters, nodes, pods are all displaying Unknown state.

To Reproduce

  • Install HA Rancher
  • Enable ui-sql-cache from Global Settings
  • Enable Server side pagination from Global settings

Result

The resources state is always Unknown

Expected Result

The actual State of Clusters, nodes, pods.

Screenshots

Screenshot from 2024-10-15 10-51-59

Screenshot from 2024-10-15 10-52-27

@izaac izaac added the kind/bug label Oct 15, 2024
@izaac izaac added this to the v2.10.0 milestone Oct 15, 2024
@izaac izaac self-assigned this Oct 15, 2024
@github-actions github-actions bot added the QA/dev-automation Issues that engineers have written automation around so QA doesn't have look at this label Oct 15, 2024
@izaac izaac changed the title Resources status are always unkown then Server Side Pagination is enabled HA Resources status are always Unkown when Server Side Pagination is enabled HA Oct 15, 2024
@gaktive gaktive changed the title Resources status are always Unkown when Server Side Pagination is enabled HA Resources status are always Unknown when Server Side Pagination is enabled HA Oct 16, 2024
@richard-cox
Copy link
Member

richard-cox commented Oct 17, 2024

@richard-cox
Copy link
Member

requires metadata.state

@richard-cox
Copy link
Member

Will be fixed when rancher/steve#300 merges (and steve in rancher/rancher is bumped). Will monitor and move to test when so

@richard-cox richard-cox modified the milestones: v2.11.0, v2.10.0 Oct 18, 2024
@richard-cox richard-cox added QA/manual-test Indicates issue requires manually testing and removed QA/dev-automation Issues that engineers have written automation around so QA doesn't have look at this labels Oct 22, 2024
@richard-cox
Copy link
Member

Given rancher/rancher#47616, moving to test

@izaac
Copy link
Contributor Author

izaac commented Oct 23, 2024

Validated on Rancher version: v2.10-24040b6dc9ae2fa6a3a49cbe126132c13c2587ba-head
Dashboard: master fa2e6dd

The resources status is now properly displayed and dynamically changed depending on their status. Tested with a pod and a cluster.

@izaac izaac closed this as completed Oct 23, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants