-
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 Installation in AWS EC2, failure to start a workspace #13690
Comments
@svkr2k how are you creating and starting the workspace? |
I think it's a duplicate of #13435 |
@benoitf Looks likey, yes. The logs here and on the other bug look uninteresting. What additional info could we request that would help us pin down the issue? |
Tentatively marking this as 7.0.0, not starting is not good. |
I suspect that @skabashnyuk @sleshchenko do you think that this may be the problem? Do you have other ideas about why wsmaster and theia cannot communicate? |
@tsmaeder , thank you for your question. Hope this helps. Thank you for looking into this. I would really be happy if i get a solution for the issue. |
@svkr2k just to clarify your environment. Are you running Che locally with minikube or on AWS? |
I experience this issue if running in multi-user mode, interestingly if I deploy Che in single-user mode Theia loads successfully, however it is then not able to create terminals. I am also using Che in AWS. |
@andy316x with which browser for terminals ? There is an issue with firefox |
@benoitf I am using Chrome so not sure if that is the problem |
I'm, running che on AWS (ubuntu 16.04) in single-user mode and created workspace using any of the already available stack/devfile from the dashboard. (Kindly note that when i run che in locally in ubuntu or windows PC, it works fine.) |
@svkr2k I have no AWS EC2 environment available to test. Can you try to install che with https://github.com/che-incubator/chectl ? |
Hi @skabashnyuk , to clarify further: I'm running Che on AWS "with minikube". |
Hi all, |
@svkr2k can you try the way to install che how @l0rd suggested here? #13838 (comment) |
@skabashnyuk , sure, i shall try that : #13838 (comment) Also, please note that in AWS EC2 instance, i start minikube using the following: |
Thank you very much for providing inputs.
~$ sudo chectl server:start --installer=helm --multiuser --platform=k8s --tls --self-signed-cert --domain=10.9.2.247.nip.io --cheimage=eclipse/che-server:7.0.0-rc-3.0
|
|
Greetings, @benoitf , @skabashnyuk . Thank you very much ! Here are the steps i followed:
Here are the other errors that i got:
|
Hi @benoitf , @skabashnyuk . |
@svkr2k I believe that this is |
@benoitf when you made your test on AWS did you use minikube aswell? |
@svkr2k when you first opened this issue you tried to install single user Che with TLS disabled. At some point though you tested with TLS and multiuser. Have you been able to solve your original problem (Che single user without tls on AWS)? I am asking because we have some open issues about deploying Che with TLS using helm charts (hence this would be a duplicate) and I would close this one if it your original issue was fixed. |
@rhopp @slemeur @tsmaeder @nickboldt I have removed the priority and the milestone here because we don't know yet if that's a duplicate, an issue that has been solved or a brand new one. |
Hi @l0rd , Thank you. But, my goal is to use hostname-based url for che. we could achieve this using defaulthost.yaml while running the helm upgrade. It would be nice if we could get the recommended practise to host che in Single-user and Multi-user modes in AWS. When we used host-based url, i could not create the workspace as the communication with the created workspace container failed. |
@svkr2k what you are describing is an existing issue about default-host/single-host: #12971. Unfortunately that's something that we haven't solved yet. We will need a few weeks to fix it properly. But, if multi-host is an option (i.e. you are ok to use a wildcard SSL certificate), it's possible to configure it with a workaround. We have an ongoing PR to avoid the workaround and make it easier to deploy Che on AWS and GCP: #12971. And in the meantime we are writing the documentation as well but we are kind of blocked by the issues above. |
So I'm closing current issue since it will be fixed by #12971 |
Description
Trying to run
che-server:7.0.0-RC-2.0
. che-server installs and runs fine, able to view dashboard and stacks/devfiles.But, when i try to create a workspace, it fails. The logs are given below.
Some of the experts in a forum feel that the che master pod is unable to communicate with the theia pod.
In local PC everyting works fine and able to create workspaces.
But, in AWS EC2, dashboard comes up, but creating workspace fails.
Reproduction Steps
OS and version:
Ubuntu 18.04
AWS EC2 instance
Diagnostics:
Here is the log:
The text was updated successfully, but these errors were encountered: