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

DevWorkspace failed to progress step "Waiting for editor to start for longer than timeout (600s)" #23276

Open
aggarwalyash opened this issue Dec 6, 2024 · 13 comments
Assignees
Labels
engine/devworkspace Issues related to Che configured to use the devworkspace controller as workspace engine. kind/question Questions that haven't been identified as being feature requests or bugs. severity/P2 Has a minor but important impact to the usage or development of the system.

Comments

@aggarwalyash
Copy link

Summary

I tried creating workspaces from the sample devfile available from the eclipse che dashboard. But after taking a lot of time they are not getting started giving me timeout error. I've already increase the timeout period to 10mins. When i try to create the empty workspace it is getting started immediately.

The more common issues i can see using the devworkspace controller events are :-

  1. Main url server is not ready.
    I don't know which main server url it is.

  2. Waiting on routing to be ready.

Relevant information

kubectl logs -f pod/devworkspace-controller-manager-596dbb747d-4xlz9 -n devworkspace-controller

{"level":"info","ts":"2024-12-05T13:36:12Z","logger":"controllers.DevWorkspace","msg":"Reconciling Workspace","Request.Namespace":"expand-my-business-che-2es8u6","Request.Name":"php-laravel","devworkspace_id":"workspacef6ebb87bc9104cf3","resolvedConfig":"workspace.progressTimeout=600s,workspace.ignoredUnrecoverableEvents=FailedScheduling"}
{"level":"info","ts":"2024-12-05T13:36:12Z","logger":"controllers.DevWorkspace","msg":"Main URL server not ready","Request.Namespace":"expand-my-business-che-2es8u6","Request.Name":"php-laravel","devworkspace_id":"workspacef6ebb87bc9104cf3","status-code":502}
{"level":"info","ts":"2024-12-05T13:36:12Z","logger":"controllers.DevWorkspace","msg":"DevWorkspace failed to start: DevWorkspace failed to progress past step 'Waiting for editor to start' for longer than timeout (600s)","Request.Namespace":"expand-my-business-che-2es8u6","Request.Name":"php-laravel","devworkspace_id":"workspacef6ebb87bc9104cf3"}

@aggarwalyash aggarwalyash added the kind/question Questions that haven't been identified as being feature requests or bugs. label Dec 6, 2024
@che-bot che-bot added the status/need-triage An issue that needs to be prioritized by the curator responsible for the triage. See https://github. label Dec 6, 2024
@AObuchow
Copy link

AObuchow commented Dec 6, 2024

If you're running Che on Kubernetes (and not OpenShift), then I suspect you're encountering #23179 (which has some workarounds provided in the issue). This bug only occurs when you're not using the UDI, and the empty workspace sample uses the UDI.

Which sample devfile are you using? Please provide the devfile :)

@AObuchow
Copy link

AObuchow commented Dec 6, 2024

From the Che Dashboard, you can provide an image for your workspace. Try using quay.io/devfile/universal-developer-image:ubi9-latest and then selecting your devfile sample. This should hopefully be a workaround, but the UDI may not have all the tools needed for that specific devfile sample.

Hopefully #23179 will eventually be resolved (if this is the root cause of your issue) -- contributions are welcome :)

@aggarwalyash
Copy link
Author

I used the following devfile https://github.com/redhat-developer/devfile-sample/blob/master/devfile.yaml

I also tried multiple samples avaiable from the che dashboard directly but each one of them is failing to run apart from the empty workspace.

@ibuziuk
Copy link
Member

ibuziuk commented Dec 9, 2024

@aggarwalyash hello, could you please clarify how you installed Eclipse Che and on what infrastructure?
also, https://github.com/redhat-developer/devfile-sample/blob/master/devfile.yaml is a very old devfile and I'm not sure if anybody support it (has not been updated for 4 years)
Please, try smth. from devfile.io registry or our Eclipse Che sample e.g. https://github.com/che-incubator/quarkus-api-example

@ibuziuk ibuziuk added engine/devworkspace Issues related to Che configured to use the devworkspace controller as workspace engine. severity/P3 Lower priority than a P2. Optional work that might get done, or not. See also help wanted issues. severity/P2 Has a minor but important impact to the usage or development of the system. and removed status/need-triage An issue that needs to be prioritized by the curator responsible for the triage. See https://github. severity/P3 Lower priority than a P2. Optional work that might get done, or not. See also help wanted issues. labels Dec 9, 2024
@ibuziuk ibuziuk self-assigned this Dec 9, 2024
@aggarwalyash
Copy link
Author

I've deployed the Eclipse che on Azure aks using the chectl tool. I followed the below link for the same
https://eclipse.dev/che/docs/next/administration-guide/installing-che-on-microsoft-azure/

@ibuziuk
Copy link
Member

ibuziuk commented Dec 10, 2024

@aggarwalyash could you please clarify if you hit this error with https://github.com/redhat-developer/devfile-sample/blob/master/devfile.yaml or other samples as well? e.g. https://github.com/che-incubator/quarkus-api-example

@ibuziuk
Copy link
Member

ibuziuk commented Dec 10, 2024

@andrewballantyne regarding https://github.com/redhat-developer/devfile-sample I believe we should either update it or archive to avoid confusion.

@aggarwalyash
Copy link
Author

aggarwalyash commented Dec 10, 2024

It is opening/creating workspace for this github repo devfile https://github.com/che-incubator/quarkus-api-example.git

But not working for https://github.com/redhat-developer/devfile-sample/blob/master/devfile.yaml

@tolusha
Copy link
Contributor

tolusha commented Dec 11, 2024

Probably registry.access.redhat.com/ubi8/nodejs-12:1-45 doesn't have all libraries to start the editor.
More samples you can find on https://registry.devfile.io/viewer

@aggarwalyash
Copy link
Author

https://registry.devfile.io/devfiles/nodejs-angular/2.2.1
https://registry.devfile.io/devfiles/python-django/2.1.0
https://registry.devfile.io/devfiles/php-laravel/2.0.1

I tried multiple earlier as well, but none of these seems to be working. Facing the same issue on all of these

@ibuziuk
Copy link
Member

ibuziuk commented Dec 11, 2024

cc: @svor maybe you have some input
AFAIK, all the devfiles from devfile.io should work

@tolusha
Copy link
Contributor

tolusha commented Dec 11, 2024

The reason is known
#23179 (comment)

@svor
Copy link
Contributor

svor commented Dec 11, 2024

cc: @svor maybe you have some input AFAIK, all the devfiles from devfile.io should work

I haven't tried devfiles from devfile.io with Che deployed on Minikube, but I can say that they work with Che on OpenShift

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
engine/devworkspace Issues related to Che configured to use the devworkspace controller as workspace engine. kind/question Questions that haven't been identified as being feature requests or bugs. severity/P2 Has a minor but important impact to the usage or development of the system.
Projects
None yet
Development

No branches or pull requests

6 participants