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.

Sign up for GitHub

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

Jump to bottom

Error message when trying to delete multiple workspaces from the Dashboard #21532

Closed
Tracked by #21799
ibuziuk opened this issue Jul 5, 2022 · 2 comments · Fixed by eclipse-che/che-dashboard#668
Closed
Tracked by #21799

Error message when trying to delete multiple workspaces from the Dashboard #21532

ibuziuk opened this issue Jul 5, 2022 · 2 comments · Fixed by eclipse-che/che-dashboard#668
Assignees
@olexii4
Labels
area/dashboard kind/bug Outline of a bug - must adhere to the bug report template. severity/P1 Has a major impact to usage or development of the system. sprint/current

Comments

@ibuziuk
Copy link
Member

ibuziuk commented Jul 5, 2022 •
edited
Loading

Describe the bug

Error message is shown when trying to delete multiple workspaces at a time from the User Dashboard on the dogfooding cluster:

Che version

7.50@latest

Steps to reproduce

Reproduced on dogfooding:

  1. Select all workspaces for deletion from UD
  2. ERROR: the error message is shown even though all workspaces are deleted correctly

Expected behavior

Workspace deleted without errors

Runtime

OpenShift

Screenshots

failure

Installation method

OperatorHub

Environment

other (please specify in additional context)

Eclipse Che Logs

No response

Additional context

Error message:

Failed to delete the workspace vaadin-demo, reason: Failed to delete workspace 'vaadin-demo'. <html> <head> <meta name="viewport" content="width=device-width, initial-scale=1"> <style type="text/css"> body { font-family: "Helvetica Neue", Helvetica, Arial, sans-serif; line-height: 1.66666667; font-size: 16px; color: #333; background-color: #fff; margin: 2em 1em; } h1 { font-size: 28px; font-weight: 400; } p { margin: 0 0 10px; } .alert.alert-info { background-color: #F0F0F0; margin-top: 30px; padding: 30px; } .alert p { padding-left: 35px; } ul { padding-left: 51px; position: relative; } li { font-size: 14px; margin-bottom: 1em; } p.info { position: relative; font-size: 20px; } p.info:before, p.info:after { content: ""; left: 0; position: absolute; top: 0; } p.info:before { background: #0066CC; border-radius: 16px; color: #fff; content: "i"; font: bold 16px/24px serif; height: 24px; left: 0px; text-align: center; top: 4px; width: 24px; } @media (min-width: 768px) { body { margin: 6em; } } </style> </head> <body> <div> <h1>Application is not available</h1> <p>The application is currently not serving requests at this endpoint. It may not have been started or is still starting.</p> <div class="alert alert-info"> <p class="info"> Possible reasons you are seeing this page: </p> <ul> <li> <strong>The host doesn't exist.</strong> Make sure the hostname was typed correctly and that a route matching this hostname exists. </li> <li> <strong>The host exists, but doesn't have a matching path.</strong> Check if the URL path was typed correctly and that the route was created using the desired path. </li> <li> <strong>Route and path matches, but all pods are down.</strong> Make sure that the resources exposed by this route (pods, services, deployment configs, etc) have at least one pod running. </li> </ul> </div> </div> </body> </html>
@ibuziuk ibuziuk added kind/bug Outline of a bug - must adhere to the bug report template. severity/P1 Has a major impact to usage or development of the system. area/dashboard sprint/next labels Jul 5, 2022
@ibuziuk ibuziuk mentioned this issue Jul 18, 2022
Closed
51 tasks
@ibuziuk ibuziuk mentioned this issue Aug 9, 2022
Closed
67 tasks
@ibuziuk ibuziuk mentioned this issue Aug 30, 2022
Closed
82 tasks
@akurinnoy akurinnoy self-assigned this Sep 12, 2022
@ibuziuk ibuziuk mentioned this issue Oct 4, 2022
Closed
59 tasks
@akurinnoy
Copy link
Contributor

I tried to reproduce this issue and repeatedly deleted dozens of workspaces at once without any problem. But I faced the same error while creating a workspace.
This problem is related to interacting with Kubernetes API: sometimes, a request fails unexpectedly. So we need to handle all requests to the Kube API and re-try them if anything's wrong, or we can also propagate a better error message to users.

@ibuziuk ibuziuk mentioned this issue Oct 18, 2022
Closed
67 tasks
@akurinnoy akurinnoy assigned olexii4 and unassigned akurinnoy Oct 19, 2022
@ibuziuk
Copy link
Member Author

ibuziuk commented Oct 20, 2022

just FYI I have reproduced the issue today on dogfooding again
image

This was referenced Nov 2, 2022
Closed
Closed
@olexii4 olexii4 mentioned this issue Nov 10, 2022
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@olexii4 olexii4

Labels
area/dashboard kind/bug Outline of a bug - must adhere to the bug report template. severity/P1 Has a major impact to usage or development of the system. sprint/current
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Add retry for Kubernetes API requests eclipse-che/che-dashboard
3 participants
@ibuziuk @olexii4 @akurinnoy