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

When workspace startup fails, propose to start it in "safe mode" #22228

Closed
l0rd opened this issue May 23, 2023 · 3 comments
Closed

When workspace startup fails, propose to start it in "safe mode" #22228

l0rd opened this issue May 23, 2023 · 3 comments
Assignees
@olexii4
Labels
area/dashboard kind/enhancement A feature request - must adhere to the feature request template. severity/P1 Has a major impact to usage or development of the system. team/A This team is responsible for the Che Operator and all its operands as well as chectl and Hosted Che

Comments

@l0rd
Copy link
Contributor

l0rd commented May 23, 2023 •
edited
Loading

Is your enhancement related to a problem? Please describe

A workspace can fail for multiple reasons:

  • vs code fails to start in the container specified in the devfile
  • the requested memory/cpu in the devfile are too large
  • the container in the devfile is terminating
  • Mounting PVs fails
  • Route or ingress creation fails
  • Git service OAuth doesn't work
  • etc...

In this case the developer doesn't have any clue how to move forward. But we can help him/her providing a minimal workspace to be able to edit the source code (and the devfile if it exist).

Describe the solution you'd like

When the workspace fails to start we should propose to the developer to start it in safe mode:

  • the devfile.yaml and .vscode/editor.yaml are not resolved (use default component, default editor)
  • no route/ingress is created (the editor endpoints with urlRewriteSupport: false are ignored)
  • ephemeral storage
  • Any operation that uses the git service REST API is avoided

Describe alternatives you've considered

No response

Additional context

No response
@l0rd l0rd added the kind/enhancement A feature request - must adhere to the feature request template. label May 23, 2023
@l0rd l0rd changed the title When a workspace fails to start we should propose to the user to start it in "safe mode" When workspace startup fails, propose to start it in "safe mode" May 23, 2023
@l0rd l0rd mentioned this issue May 23, 2023
Closed
@l0rd l0rd added area/dashboard severity/P1 Has a major impact to usage or development of the system. labels May 23, 2023
@ibuziuk
Copy link
Member

ibuziuk commented Jul 13, 2023

After the discussion the issue boils down to the following user story "As a user when workspace fails to start I should always have the option to start with the default devfile". Currently, this possibility is missing on the UI:

image

@ibuziuk ibuziuk added the team/A This team is responsible for the Che Operator and all its operands as well as chectl and Hosted Che label Jul 13, 2023
@ibuziuk ibuziuk moved this to Unplanned Tasks in Eclipse Che Team A Backlog Jul 13, 2023
@ibuziuk ibuziuk moved this from Unplanned Tasks to 🚧 In Progress in Eclipse Che Team A Backlog Jul 26, 2023
@olexii4 olexii4 mentioned this issue Aug 2, 2023
Merged
@ibuziuk ibuziuk mentioned this issue Aug 4, 2023
Closed
@olexii4 olexii4 mentioned this issue Aug 14, 2023
Merged
@olexii4 olexii4 moved this from 🚧 In Progress to Ready for Review in Eclipse Che Team A Backlog Aug 16, 2023
@ibuziuk ibuziuk moved this from Ready for Review to ✅ Done in Eclipse Che Team A Backlog Aug 31, 2023
@ibuziuk ibuziuk moved this from ✅ Done to 🚧 In Progress in Eclipse Che Team A Backlog Aug 31, 2023
@ibuziuk ibuziuk mentioned this issue Sep 27, 2023
Closed
@ibuziuk
Copy link
Member

ibuziuk commented Sep 27, 2023

After a discussion with @l0rd it was decided to close this issue since the main safe mode functionality is implemented and open separate issues with enhancements e.g. #22561

@ibuziuk ibuziuk closed this as completed Sep 27, 2023
@ibuziuk ibuziuk moved this from 🚧 In Progress to ✅ Done in Eclipse Che Team A Backlog Sep 27, 2023
@l0rd
Copy link
Contributor Author

l0rd commented Sep 27, 2023

I just sent a note to the che-dev mailing list about that.

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/enhancement A feature request - must adhere to the feature request template. severity/P1 Has a major impact to usage or development of the system. team/A This team is responsible for the Che Operator and all its operands as well as chectl and Hosted Che
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@l0rd @ibuziuk @olexii4