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

Rancher Error when browsing clusters and refreshing #4967

Closed
gaktive opened this issue Jan 20, 2022 · 3 comments · Fixed by #5319
Closed

Rancher Error when browsing clusters and refreshing #4967

gaktive opened this issue Jan 20, 2022 · 3 comments · Fixed by #5319

Comments

@gaktive
Copy link
Member

gaktive commented Jan 20, 2022

Internal reference: SURE-3907
Reported in 2.6.3

A user is seeing an issue with the new Interface where when browsing to a cluster and hitting refresh the Default backend error screen will appear.

It is triggered by, clicking into a cluster, then hitting F5. usually the first time,

What's likely missing is the schema for that type in the body of the response for the request to /k8s/clusters/(id)/v1/schemas

Attached are some screenshots.

ranchererror.pngScreen Shot 2022-01-07 at 1.38.00 PM.pngScreen Shot 2022-01-07 at 1.38.36 PM.png

@gaktive
Copy link
Member Author

gaktive commented Feb 24, 2022

@nwmac has been able to repro but it's a tight window to capture it as the cluster comes up. It may take time to troubleshoot though since there's a lot of tear down required, but we need to handle this race condition with something to display and then a retry.

@nwmac
Copy link
Member

nwmac commented Mar 1, 2022

@gaktive I tried again to reproduce and could not - previously I could deploy the docker AIO image and if I quickly logged in and tried to explore the cluster, I got the fail-whale page.

@sowmyav27
Copy link

On 2.6-head commit id: f904267

  • Refreshed webpage after cluster creation, after scaling down/up nodes.
  • This error is not seen
  • Tried multiple times.
  • Will close the issue now. Will lo a new one if this is seen again.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants