eclipse-che / che

Kubernetes based Cloud Development Environments for Enterprise Teams
http://eclipse.org/che
Eclipse Public License 2.0
6.99k stars 1.19k forks source link

Need help to setup Eclipse-che 7 on Openshift 3 #15481

Closed svrajasekar closed 4 years ago

svrajasekar commented 4 years ago

I have been trying hard to setup Eclipse-che on Openshift 3 over the last few days. But could not successfully do it.

I tried in Minikube, Minishift, Kubernetes and Openshift. It failed in all.

Che-server pod crashes in multiuser mode. I tried with various versions of Openshift and Eclipse che. But no use.

I am able to start Eclipse-che in single user mode. But in multiuser mode, che-server pod crashes.

I need help desperately.

svrajasekar commented 4 years ago

@tag-ii Could you create a workspace?. If not, please try that. Also as which user did you login to web console?. developer?. Is it through the console that you created users, roles and project che? As developer user, did it allow you to create users and roles?.

Before typing chectl ...., did you login as developer or system:admin?

Pls don't think I am asking too many questions. I have been banging my head on this for more than 3 weeks. My company is steam-rolling me everyday asking for status.

Please respond,

tag-ii commented 4 years ago

Ok, so as far as I could get yesterday, the che server pod crashed in the process of starting a workspace.

I initially logged into the web console as user just to verify it was working. I then logged into oc as system:admin and created another user and assigned it the cluster admin role. That user is the one I then used to install che with chectl.

No problem with the questions. We're all trying to get it going.

I'm just getting back to it now myself. I'll update here if I'm able to discover what caused the che server to crash or if I'm able to get a workspace going.

che-bot commented 4 years ago

Issues go stale after 180 days of inactivity. lifecycle/stale issues rot after an additional 7 days of inactivity and eventually close.

Mark the issue as fresh with /remove-lifecycle stale in a new comment.

If this issue is safe to close now please do so.

Moderators: Add lifecycle/frozen label to avoid stale mode.