Che: Unable to shutdown server or login with chectl on windows 10 home

Created on 12 Nov 2020  ยท  4Comments  ยท  Source: eclipse/che

Describe the bug


I am attempting to run chectl server:stop to shutdown my server safely. When I do so, I am presented with an error:

chectl server:stop
โ€บ Current Kubernetes context: 'docker-desktop'
  โˆš Verify Kubernetes API...OK
  โˆš Verify if Eclipse Che is deployed into namespace "che"
    โˆš Found running Eclipse Che deployment
    โˆš Found running postgres deployment
    โˆš Found running keycloak deployment
    โˆš Found running plugin registry deployment
    โˆš Found running devfile registry deployment
  โˆš Check Eclipse Che server status...RUNNING (auth enabled)
  ร— Stop Eclipse Che server and wait until it's ready to shutdown
    โ†’ E_SHUTDOWN_CHE_SERVER_FAIL - Failed to shutdown Eclipse Che server. Login context is not set. Please login first.
    Scale "che" deployment to zero
    Scale "keycloak" deployment to zero
    Scale "postgres" deployment to zero
    Scale "devfile registry" deployment to zero
    Scale "plugin registry" deployment to zero
    Wait until Eclipse Che pod is deleted
    Wait until Keycloak pod is deleted
    Wait until Postgres pod is deleted
    Wait until Devfile registry pod is deleted
    Wait until Plugin registry pod is deleted
 ยป   Error: E_SHUTDOWN_CHE_SERVER_FAIL - Failed to shutdown Eclipse Che server. Login context is not set. Please login
 ยป   first.

So I attempted to run chectl auth:login and was presetnted with another error:

chectl auth:login
โ€บ Current Kubernetes context: 'docker-desktop'
Using https://che-che.169.254.45.252.nip.io/api server API URL to log in
    Error: Command failed with exit code 1: oc status
    error: you do not have rights to view project "default" specified in your config or the project doesn't exist

I've looked through the documentation, and there isn't any way to create a default project or give me rights to it.

Che version

  • [X] latest (7.22.0-SNAPSHOT)
  • [ ] nightly
  • [ ] other: please specify

Steps to reproduce

  1. Run chectl server:deploy --platform=docker-desktop
  2. Run chectl server:stop
  3. Run chectl auth:login

Expected behavior


I expected the server to shutdown, or to properly login to be able to shutdown the server.

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)
  • [X] docker-desktop + K8S (include output of docker version and kubectl version)
docker version
Client: Docker Engine - Community
 Cloud integration: 1.0.2
 Version:           19.03.13
 API version:       1.40
 Go version:        go1.13.15
 Git commit:        4484c46d9d
 Built:             Wed Sep 16 17:00:27 2020
 OS/Arch:           windows/amd64
 Experimental:      false

Server: Docker Engine - Community
 Engine:
  Version:          19.03.13
  API version:      1.40 (minimum version 1.12)
  Go version:       go1.13.15
  Git commit:       4484c46d9d
  Built:            Wed Sep 16 17:07:04 2020
  OS/Arch:          linux/amd64
  Experimental:     false
 containerd:
  Version:          v1.3.7
  GitCommit:        8fba4e9a7d01810a393d5d25a3621dc101981175
 runc:
  Version:          1.0.0-rc10
  GitCommit:        dc9208a3303feef5b3839f4323d9beb36df0a9dd
 docker-init:
  Version:          0.18.0
  GitCommit:        fec3683
kubectl version
Client Version: version.Info{Major:"1", Minor:"19", GitVersion:"v1.19.3", GitCommit:"1e11e4a2108024935ecfcb2912226cedeafd99df", GitTreeState:"clean", BuildDate:"2020-10-14T12:50:19Z", GoVersion:"go1.15.2", Compiler:"gc", Platform:"windows/amd64"}
Server Version: version.Info{Major:"1", Minor:"19", GitVersion:"v1.19.3", GitCommit:"1e11e4a2108024935ecfcb2912226cedeafd99df", GitTreeState:"clean", BuildDate:"2020-10-14T12:41:49Z", GoVersion:"go1.15.2", Compiler:"gc", Platform:"linux/amd64"}



md5-99e49a97fb33e38a2b6b0086561ea553



chectl server:deploy --platform=docker-desktop
โ€บ Current Kubernetes context: 'docker-desktop'
โ€บ Installer type is set to: 'operator'
  โˆš Verify Kubernetes API...OK
  โˆš ๏ฟฝ  Looking for an already existing Eclipse Che instance
    โˆš Verify if Eclipse Che is deployed into namespace "che"...it is not
  โˆš โœˆ๏ธ  Docker Desktop preflight checklist
    โˆš Verify if kubectl is installed
    โˆš Verify if kubectl context is Docker Desktop: Found docker-desktop.
    โˆš Verify remote kubernetes status...done.
    โˆš Check Kubernetes version: Found v1.19.3.
    โˆš Verify if nginx ingress is installed
    โˆš Installing nginx ingress
    โˆš Verify domain is set... auto-assigning domain to 169.254.45.252.nip.io....set to 169.254.45.252.nip.io.
  โˆš Start following logs
    โˆš Start following Operator logs...done
    โˆš Start following Eclipse Che logs...done
    โˆš Start following Postgres logs...done
    โˆš Start following Keycloak logs...done
    โˆš Start following Plugin registry logs...done
    โˆš Start following Devfile registry logs...done
  โˆš Start following events
    โˆš Start following namespace events...done
  โˆš ๏ฟฝโ€  Running the Eclipse Che operator
    โˆš Copying operator resources...done.
    โˆš Create Namespace (che)...Done.
    โˆš Create ServiceAccount che-operator in namespace che...done.
    โˆš Create Role che-operator in namespace che...done.
    โˆš Create ClusterRole che-che-operator...done.
    โˆš Create RoleBinding che-operator in namespace che...done.
    โˆš Create ClusterRoleBinding che-che-operator...done.
    โˆš Create CRD checlusters.org.eclipse.che...done.
    โˆš Waiting 5 seconds for the new Kubernetes resources to get flushed...done.
    โˆš Create deployment che-operator in namespace che...done.
    โˆš Operator pod bootstrap
      โˆš Scheduling...done
      โˆš Downloading images...done
      โˆš Starting...done
    โˆš Prepare Eclipse Che cluster CR...Done.
    โˆš Create the Custom Resource of type checlusters.org.eclipse.che in the namespace che...done.
  โˆš โœ…  Post installation checklist
    โˆš PostgreSQL pod bootstrap
      โˆš Scheduling...done
      โˆš Downloading images...done
      โˆš Starting...done
    โˆš Keycloak pod bootstrap
      โˆš Scheduling...done
      โˆš Downloading images...done
      โˆš Starting...done
    โˆš Devfile registry pod bootstrap
      โˆš Scheduling...done
      โˆš Downloading images...done
      โˆš Starting...done
    โˆš Plugin registry pod bootstrap
      โˆš Scheduling...done
      โˆš Downloading images...done
      โˆš Starting...done
    โˆš Eclipse Che pod bootstrap
      โˆš Scheduling...done
      โˆš Downloading images...done
      โˆš Starting...done
    โˆš Eclipse Che status check
  โˆš Retrieving Keycloak admin credentials...done
  โˆš Retrieving Che self-signed CA certificate... done
  โˆš Prepare post installation output...done
  โˆš Show important messages
    โˆš Eclipse Che 7.22.0-SNAPSHOT has been successfully deployed.
    โˆš Documentation             : https://www.eclipse.org/che/docs/
    โˆš -------------------------------------------------------------------------------
    โˆš Users Dashboard           : https://che-che.169.254.45.252.nip.io
    โˆš -------------------------------------------------------------------------------
    โˆš Plug-in Registry          : https://plugin-registry-che.169.254.45.252.nip.io/v3
    โˆš Devfile Registry          : https://devfile-registry-che.169.254.45.252.nip.io
    โˆš -------------------------------------------------------------------------------
    โˆš Identity Provider URL     : https://keycloak-che.169.254.45.252.nip.io/auth
    โˆš Identity Provider login   : "admin:ehfNVt7cV2Bf".
    โˆš -------------------------------------------------------------------------------
    โˆš [ACTION REQUIRED] Please add Che self-signed CA certificate into your browser: C:\Users\samti\AppData\Local\Temp\
cheCA.crt.
   Documentation how to add a CA certificate into a browser: https://www.eclipse.org/che/docs/che-7/overview/importing-
certificates-to-browsers/
Command server:deploy has completed successfully in 05:42.



md5-c1d0a178d575991b9fb1cacf088f32ca



chectl version
chectl/0.0.20201110-next.4213cef win32-x64 node-v10.23.0
  • [ ] OperatorHub
  • [ ] I don't know

Environment

  • [ ] my computer

    • [X] Windows 10 Home edition

    • [ ] Linux

    • [ ] macOS

  • [ ] Cloud

    • [ ] Amazon

    • [ ] Azure

    • [ ] GCE

    • [ ] other (please specify)

  • [ ] other: please specify

Eclipse Che Logs


che.zip

Additional context


I am using Windows 10 home, and as all of the other methods I've tried to deploy the server require Hyper-V, Docker is my only option.

arechectl kinbug severitP1

Most helpful comment

PR is merged.

All 4 comments

@theMcQ
auth:login command should ask for user/password instead of failing.
Will be fixed by this https://github.com/che-incubator/chectl/pull/988
Meanwhile try in the following way:
chectl auth:login -u <user> -p <password>

Not sure why I got tagged on this. I'm PMC lead for the Eclipse Project and a committer on Orion, but I haven't done more than "try it" with Che.

Using chectl auth:login -u <user> -p <password> worked, and I was able to shutdown safely. I'll leave this open until che-incubator/chectl#988 is merged, as the original use of chectl auth:login is still broken.

PR is merged.

Was this page helpful?
0 / 5 - 0 ratings