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

Impossible to start workspace #14336

Closed
5 of 23 tasks
vitaliy-guliy opened this issue Aug 27, 2019 · 2 comments
Closed
5 of 23 tasks

Impossible to start workspace #14336

vitaliy-guliy opened this issue Aug 27, 2019 · 2 comments
Labels
severity/blocker Causes system to crash and be non-recoverable or prevents Che developers from working on Che code.
Milestone

Comments

@vitaliy-guliy
Copy link
Contributor

vitaliy-guliy commented Aug 27, 2019

Describe the bug

After restarting the minikube with existing Che workspace I was not able to continue my work.
Che server was failing with the following error

Screenshot from 2019-08-27 10-20-37

Then I

  • stopped and deleted running minikube by commands minikube stop and minikube delete
  • deleted all local docker images/containers
  • updated chectl to the latest version
  • started minikube with a command minikube start --memory=10240 --cpus=4 --disk-size=20g
  • started Che server by chectl server:start
  • created a workspace from NodeJS Express Web Application stack (tried also to use devfile)

My workspace always fails

Screenshot from 2019-08-27 11-19-14

Screenshot from 2019-08-27 11-21-44

Che version

  • latest
  • nightly
  • other: please specify

Steps to reproduce

Described in the issue description

Expected behavior

Running workspace

Runtime

  • kubernetes (include output of kubectl version)
  • Openshift (include output of oc version)
  • minikube (include output of minikube version and kubectl version)
  • minishift (include output of minishift version and oc version)
  • docker-desktop + K8S (include output of docker version and kubectl version)
  • other: (please specify)

Installation method

  • chectl
  • che-operator
  • minishift-addon
  • I don't know

Environment

  • my computer
    • Windows
    • Linux
    • macOS
  • Cloud
    • Amazon
    • Azure
    • GCE
    • other (please specify)
  • other: please specify

This is blocker for IDE2 team as we are using Che for daily work.

@vitaliy-guliy vitaliy-guliy added the severity/blocker Causes system to crash and be non-recoverable or prevents Che developers from working on Che code. label Aug 27, 2019
@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 Aug 27, 2019
@metlos
Copy link
Contributor

metlos commented Aug 27, 2019

As a workaround, please add this env var to the configuration of the che server:

CHE_INFRA_KUBERNETES_INGRESS_PATH__TRANSFORM=%s

The fix will follow rather quickly...

@metlos
Copy link
Contributor

metlos commented Aug 27, 2019

Note that if chectl used the latest helm chart, you shouldn't have seen this issue (https://github.com/eclipse/che/blob/master/deploy/kubernetes/helm/che/templates/configmap.yaml#L75)

metlos added a commit to metlos/che that referenced this issue Aug 27, 2019
Don't blow up on missing path transform configuration.

Signed-off-by: Lukas Krejci <[email protected]>
@skabashnyuk skabashnyuk added this to the 7.1.0 milestone Aug 27, 2019
@metlos metlos closed this as completed in a291807 Aug 27, 2019
@metlos metlos removed the status/need-triage An issue that needs to be prioritized by the curator responsible for the triage. See https://github. label Aug 27, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
severity/blocker Causes system to crash and be non-recoverable or prevents Che developers from working on Che code.
Projects
None yet
Development

No branches or pull requests

4 participants