Che is not accessible after being started by chectl on Kubernetes

Describe the bug

Chectl didn’t enable ingress addon on Kubernetes besides there was Enable minikube ingress addon [completed] in output, and it made Che inaccessible by Che Server URL.

Chectl version

https://github.com/che-incubator/chectl/releases/latest/download/chectl-linux

Steps to reproduce

1. Install Kubernetes using minikube from scratch:

  export MINIKUBE_WANTUPDATENOTIFICATION=false
  export MINIKUBE_WANTREPORTERRORPROMPT=false
  export MINIKUBE_HOME=$HOME
  export CHANGE_MINIKUBE_NONE_USER=true
  export KUBECONFIG=$HOME/.kube/config
  
  mkdir -p $HOME/.kube $HOME/.minikube
  touch $KUBECONFIG
  
  sudo -E  /usr/local/bin/minikube start  \
      --vm-driver=none \
      --cpus 4 \
      --memory 12288 \
      --extra-config=kubelet.cgroup-driver=systemd

1. Start Che using chectl:

chectl server:start --k8spodreadytimeout=180000 -t=/mnt/hudson_workspace/workspace/CHE-7-Happy-Path-Tests/deploy/ --listr-renderer=verbose

Expected behavior

Che has been installed and is accessible by Che Server URL.

Actual behavior

Che was not accessible by Che Server URL because ingress addon was not actually enabled:

curl -v http://che-che.10.0.148.224.nip.io
* About to connect() to che-che.10.0.148.224.nip.io port 80 (#0)
*   Trying 10.0.148.224...
* Connection refused
* Failed connect to che-che.10.0.148.224.nip.io:80; Connection refused
* Closing connection 0
curl: (7) Failed connect to che-che.10.0.148.224.nip.io:80; Connection refused

There was no ~/.minikube/config/config.json file with "ingress": true parameter

ls -la ~/.minikube/config
total 4
drwxr-xr-x.  2 hudson hudson    6 Jul 12 12:07 .
drwxrwxr-x. 10 hudson hudson 4096 Jul 12 12:07 ..

There was no nginx-ingress-controller running among the pods:

kubectl get pods --all-namespaces
NAMESPACE     NAME                               READY   STATUS    RESTARTS   AGE
che           che-6d6c8b5fb4-rbnr2               1/1     Running   0          3m36s
kube-system   coredns-fb8b8dccf-75bs8            1/1     Running   0          6m23s
kube-system   coredns-fb8b8dccf-nqr5s            1/1     Running   0          6m23s
kube-system   etcd-minikube                      1/1     Running   0          5m9s
kube-system   kube-addon-manager-minikube        1/1     Running   0          6m33s
kube-system   kube-apiserver-minikube            1/1     Running   0          5m21s
kube-system   kube-controller-manager-minikube   1/1     Running   0          5m34s
kube-system   kube-proxy-pfq2l                   1/1     Running   0          6m23s
kube-system   kube-scheduler-minikube            1/1     Running   0          5m29s
kube-system   storage-provisioner                1/1     Running   0          6m22s
kube-system   tiller-deploy-75456b7758-7v9lj     1/1     Running   0          3m54s

Runtime

• kubernetes

Client Version: version.Info{Major:“1”, Minor:“14”, GitVersion:“v1.14.3”, GitCommit:“5e53fd6bc17c0dec8434817e69b04a25d8ae0ff0”, GitTreeState:“clean”, BuildDate:“2019-06-06T01:44:30Z”, GoVersion:“go1.12.5”, Compiler:“gc”, Platform:“linux/amd64”}

• minikube v1.1.1, kubelet v1.14.3

Logs

/usr/local/bin/chectl server:start --k8spodreadytimeout=180000 -t=/mnt/hudson_workspace/workspace/CHE-7-Happy-Path-Tests/deploy/ --listr-renderer=verbose
[12:10:00] ✈️  Minikube preflight checklist [started]
[12:10:00] Verify if kubectl is installed [started]
[12:10:00] Verify if kubectl is installed [completed]
[12:10:00] Verify if minikube is installed [started]
[12:10:00] Verify if minikube is installed [completed]
[12:10:00] Verify if minikube is running [started]
[12:10:00] Verify if minikube is running [completed]
[12:10:00] Start minikube [started]
[12:10:00] Start minikube [skipped]
[12:10:00] → Minikube is already running.
[12:10:00] Verify if minikube ingress addon is enabled [started]
[12:10:00] Verify if minikube ingress addon is enabled [completed]
[12:10:00] Enable minikube ingress addon [started]
[12:10:00] Enable minikube ingress addon [completed]
[12:10:00] Retrieving minikube IP and domain for ingress URLs [started]
[12:10:00] Retrieving minikube IP and domain for ingress URLs...10.0.148.224.nip.io. [title changed]
[12:10:00] Retrieving minikube IP and domain for ingress URLs...10.0.148.224.nip.io. [completed]
[12:10:00] ✈️  Minikube preflight checklist [completed]
[12:10:00] 🏃‍  Running Helm to install Che [started]
[12:10:00] Verify if helm is installed [started]
[12:10:00] Verify if helm is installed [completed]
[12:10:00] Create Tiller Role Binding [started]
[12:10:01] Create Tiller Role Binding...done. [title changed]
[12:10:01] Create Tiller Role Binding...done. [completed]
[12:10:01] Create Tiller Service Account [started]
[12:10:01] Create Tiller Service Account...done. [title changed]
[12:10:01] Create Tiller Service Account...done. [completed]
[12:10:01] Create Tiller RBAC [started]
[12:10:01] Create Tiller RBAC [completed]
[12:10:01] Create Tiller Service [started]
[12:10:08] Create Tiller Service...done. [title changed]
[12:10:08] Create Tiller Service...done. [completed]
[12:10:08] Preparing Che Helm Chart [started]
[12:10:08] Preparing Che Helm Chart...done. [title changed]
[12:10:08] Preparing Che Helm Chart...done. [completed]
[12:10:08] Updating Helm Chart dependencies [started]
[12:10:13] Updating Helm Chart dependencies...done. [title changed]
[12:10:13] Updating Helm Chart dependencies...done. [completed]
[12:10:13] Deploying Che Helm Chart [started]
[12:10:13] Deploying Che Helm Chart...done. [title changed]
[12:10:13] Deploying Che Helm Chart...done. [completed]
[12:10:13] 🏃‍  Running Helm to install Che [completed]
[12:10:13] ✅  Post installation checklist [started]
[12:10:13] Che pod bootstrap [started]
[12:10:13] scheduling [started]
[12:10:13] scheduling...done. [title changed]
[12:10:13] scheduling...done. [completed]
[12:10:13] downloading images [started]
[12:10:26] downloading images...done. [title changed]
[12:10:26] downloading images...done. [completed]
[12:10:26] starting [started]
[12:10:48] starting...done. [title changed]
[12:10:48] starting...done. [completed]
[12:10:48] Che pod bootstrap [completed]
[12:10:48] Retrieving Che Server URL [started]
[12:10:48] Retrieving Che Server URL...http://che-che.10.0.148.224.nip.io [title changed]
[12:10:48] Retrieving Che Server URL...http://che-che.10.0.148.224.nip.io [completed]
[12:10:48] Che status check [started]
[12:10:48] Che status check [completed]
[12:10:48] ✅  Post installation checklist [completed]

Full build log: https://codeready-workspaces-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/che7-e2e-tests/job/CHE-7-Happy-Path-Tests/338/

Installation method

• chectl

Environment

• OpenStack on CRW Central CI
  • RHEL 7.4

[michealharrington]

I’m still having the same issue.

minikube version
minikube version: v1.10.1
commit: 63ab801ac27e5742ae442ce36dff7877dcccb278

chectl server:start --platform minikube --installer=helm
› Current Kubernetes context: 'minikube'
  ✔ Verify Kubernetes API...OK
  ✔ 👀  Looking for an already existing Eclipse Che instance
    ✔ Verify if Eclipse Che is deployed into namespace "che"...it is not
  ✔ ✈️  Minikube preflight checklist
    ✔ Verify if kubectl is installed
    ✔ Verify if minikube is installed
    ✔ Verify if minikube is running
    ↓ Start minikube [skipped]
      → Minikube is already running.
    ✔ Check Kubernetes version: Found v1.18.2.
    ✔ Verify if minikube ingress addon is enabled
    ✔ Enable minikube ingress addon
    ✔ Retrieving minikube IP and domain for ingress URLs...172.17.0.4.nip.io.
    ↓ Check if cluster accessible [skipped]
Eclipse Che logs will be available in '/tmp/chectl-logs/1590608546255'
  ✔ Start following logs
    ↓ Start following Operator logs [skipped]
    ✔ 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
 ›   Warning: You can also use features rich 'OLM' installer to deploy Eclipse Che.
  ✔ 🏃‍  Running Helm to install Eclipse Che
    ✔ Verify if helm is installed
    ✔ Check Helm Version: Found v3.2.0+ge11b7ce
    ✔ Create Namespace (che)...done.
    ✔ Check Eclipse Che TLS certificate...going to generate self-signed one
      ✔ Check Cert Manager deployment...not deployed
      ✔ Deploy cert-manager...done
      ✔ Wait for cert-manager...ready
      ✔ Check Cert Manager CA certificate...generating new one
      ✔ Set up Eclipse Che certificates issuer...done
      ✔ Request self-signed certificate...done
      ✔ Wait for self-signed certificate...ready
      ✔ Retrieving Che self-signed CA certificate... is exported to /home/<>/cheCA.crt
    ✔ Check Cluster Role Binding...does not exists.
    ✔ Preparing Eclipse Che Helm Chart...done.
    ✔ Updating Helm Chart dependencies...done.
    ✔ Deploying Eclipse Che Helm Chart...done.
  ✔ ✅  Post installation checklist
    ✔ 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.
    ✔ Retrieving Eclipse Che server URL... https://che-che.172.17.0.4.nip.io
    ✔ Eclipse Che status check
  ✔ Show important messages
    ✔ ❗[MANUAL ACTION REQUIRED] Please add Che self-signed CA certificate into your browser: /home/<>/cheCA.crt.
   Documentation how to add a CA certificate into a browser: https://www.eclipse.org/che/docs/che-7/installing-che-in-tls-mode-with-self-signed-certificates/#using-che-with-tls_installing-che-in-tls-mode-with-se
lf-signed-certificates
Command server:start has completed successfully.

curl -v https://che-che.172.17.0.4.nip.io
* Could not resolve host: che-che.172.17.0.4.nip.io
* Closing connection 0
curl: (6) Could not resolve host: che-che.172.17.0.4.nip.io

How do I make https://che-che.172.17.0.4.nip.io accessible to the host machine? Hitting 172.17.0.4 hits an nginx, which means I must be close, but the nip.io doesn’t seem to work for me.

I’ll gladly give anymore information that is needed.

[che-bot]

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.