-
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
Eclipse Che: Workspace is not getting created - DevWorkspace failed to progress past step 'Waiting for editor to start' for longer than timeout (300s) #22880
Comments
@debkantap |
@debkantap
|
@RomanNikitenko ..I am using "Maven Java" from devfile.io kubectl logs -n devworkspace-controller deploy/devworkspace-controller-manager -f --output------ --output---- kubectl get events -n debkanta-pramanick-pil-com-che-p0nfvh ----------------------------output----------------------- LAST SEEN TYPE REASON OBJECT MESSAGE ----------------------------output----------------------- |
@RomanNikitenko |
I think it fails here at |
Only the root user can write
As @tolusha commented, this issue will be reproduced only on vanilla Kubernetes. |
I believe I'm running into this issue - I can start a VS Code workspace by cloning an existing Github repo without a devfile, and it also works fine when I start an empty workspace, but trying to start the "Maven + Java" example or the "Python" example will produce these errors in the
I am running Che on Minikube in an Apple Silicon machine (using https://github.com/chipmk/docker-mac-net-connect to resolve the Minikube ingress issues on MacOS). Is there anything we can do, besides running OpenShift instead of Minikube? |
I tried OpenShift Local, and I saw the same behaviour where the "Python" / "Maven + Java" examples would be stuck with the same messages as above, whereas creating an empty workspace worked as usual. OpenShift's console was a bit more helpful and did show the hook that was being executed at PostStart time, so I looked at the
It seems to be due to my use of an Apple Silicon machine, which may be complicating things. I verified the same problem in Minikube:
I'll remove myself from this discussion then, as it seems my issue is different than the one in this issue. |
@agarciadom the issue you're describing above seems to reassemble a bug I've been trying to figure out: #23179. I think that bug may be a better place to discuss your issue. I'm not certain, but the issue you're encountering might have to do with the UBI9 image used for the workspace (in the devfile) since you reported that the empty workspace sample works (which uses the UDI image instead). Thank you so much for reporting your findings! |
Summary
I am running Eclipse che verion 7.82 on k8s. This is using workspace template from devfile.io.
While creating the devworksapces from the devfile hosted on devfile.io, I am getting the timeout error. This is the error coming in close: "DevWorkspace failed to progress past step 'Waiting for editor to start' for longer than timeout (300s)"
I am not able to get any error from log from backend (my bad probably).
However if I try to create the devworkspace from the devfile hosted in embedded devfile registry, it is working.
Relevant information
No response
The text was updated successfully, but these errors were encountered: