-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Comments
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 :) |
From the Che Dashboard, you can provide an image for your workspace. Try using Hopefully #23179 will eventually be resolved (if this is the root cause of your issue) -- contributions are welcome :) |
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. |
@aggarwalyash hello, could you please clarify how you installed Eclipse Che and on what infrastructure? |
I've deployed the Eclipse che on Azure aks using the chectl tool. I followed the below link for the same |
@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 |
@andrewballantyne regarding https://github.com/redhat-developer/devfile-sample I believe we should either update it or archive to avoid confusion. |
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 |
Probably |
https://registry.devfile.io/devfiles/nodejs-angular/2.2.1 I tried multiple earlier as well, but none of these seems to be working. Facing the same issue on all of these |
cc: @svor maybe you have some input |
The reason is known |
I haven't tried devfiles from devfile.io with Che deployed on Minikube, but I can say that they work with Che on OpenShift |
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 :-
Main url server is not ready.
I don't know which main server url it is.
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"}
The text was updated successfully, but these errors were encountered: