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

Cluster Explorer: Nodes: Error thrown after navigating away from the nodes details page #12292

Open
yonasberhe23 opened this issue Oct 18, 2024 · 2 comments · May be fixed by #12296
Open

Cluster Explorer: Nodes: Error thrown after navigating away from the nodes details page #12292

yonasberhe23 opened this issue Oct 18, 2024 · 2 comments · May be fixed by #12296
Assignees
Labels
area/vue3 Bugs and technical debts as outcome to the Vue3 migration kind/bug QA/dev-automation Issues that engineers have written automation around so QA doesn't have look at this
Milestone

Comments

@yonasberhe23
Copy link
Contributor

Setup

  • Rancher version: v2.10
  • Rancher UI Extensions:
  • Browser type & version: FF, Chrome

Describe the bug
Error is thrown after navigating away from the nodes details page.

Error encountered while polling Error: Unknown schema for type: metrics.k8s.io.nodemetrics

To Reproduce

Result
Error is thrown after navigating away from the nodes details page.

Expected Result
No error is thrown after navigating away from the nodes details page.

Screenshots

Screen.Recording.2024-10-17.at.5.12.37.PM.mov

Additional context

@yonasberhe23 yonasberhe23 added kind/bug area/vue3 Bugs and technical debts as outcome to the Vue3 migration labels Oct 18, 2024
@yonasberhe23 yonasberhe23 added this to the v2.10.0 milestone Oct 18, 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 18, 2024
@rak-phillip rak-phillip self-assigned this Oct 18, 2024
@rak-phillip
Copy link
Member

@yonasberhe23 I'm not able to reproduce this issue. Can you provide more details on how we can get a repro? Otherwise, I might need access to your environment to better understand the failure.

@rak-phillip
Copy link
Member

Hmmm it looks like I was able to trigger a repro while testing another issue. Will be taking a closer look

Image

@rak-phillip rak-phillip linked a pull request Oct 18, 2024 that will close this issue
7 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/vue3 Bugs and technical debts as outcome to the Vue3 migration kind/bug QA/dev-automation Issues that engineers have written automation around so QA doesn't have look at this
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants