[chectl]- Not able to to deploy Eclipse Che using operator installer

Describe the bug

Chectl fails to install when operator installer. Installation logs:

[flacatusu@localhost Downloads]$ chectl server:deploy --installer=operator --platform=minikube › 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.20.0. ✔ Verify if minikube ingress addon is enabled ↓ Enable minikube ingress addon [skipped] → Ingress addon is already enabled. ✔ Retrieving minikube IP and domain for ingress URLs…192.168.49.2.nip.io. ✔ Checking minikube version… 1.16.0 ↓ Check if cluster accessible [skipped] ✔ Following Eclipse Che logs ✔ Start following Operator logs…done ✔ Start following Eclipse Che server 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 namespace events…done ❯ 🏃‍ Running the Eclipse Che operator ✔ Copying operator resources…done. ✔ Create Namespace (che)…It already exists. ✔ Create ServiceAccount che-operator in namespace che…done. ✔ Create Role che-operator in namespace che…done. ✔ Create ClusterRole che-che-operator…done. ✔ Create ClusterRole che-che-namespace-editor…done. ✔ Create ClusterRoleBinding che-che-operator-namespace-editor…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…failed → Failed to start a pod, reason: Completed Prepare Eclipse Che cluster CR › Error: Error: Failed to start a pod, reason: Completed › Command server:deploy failed. Error log: /home/flacatusu/.cache/chectl/error.log

EVENTS:

eclipse-che   2m7s        Normal    Pulled                    pod/che-operator-5c7fb97d6c-z5xfx                Successfully pulled image "quay.io/eclipse/che-operator:nightly" in 178.53657ms
eclipse-che   28s         Warning   Unhealthy                 pod/che-operator-5c7fb97d6c-z5xfx                Readiness probe failed: Get "http://172.17.0.3:6789/healthz": dial tcp 172.17.0.3:6789: connect: connection refused
eclipse-che   22s         Warning   Unhealthy                 pod/che-operator-5c7fb97d6c-z5xfx                Liveness probe failed: Get "http://172.17.0.3:6789/readyz": dial tcp 172.17.0.3:6789: connect: connection refused
eclipse-che   22s         Normal    Killing                   pod/che-operator-5c7fb97d6c-z5xfx                Container che-operator failed liveness probe, will be restarted

Che version

• latest
• [X ] nightly
• other: please specify

Steps to reproduce

Expected behavior

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)

Screenshots

Installation method

• [X ] chectl
  • provide a full command that was used to deploy Eclipse Che (including the output)
  • provide an output of chectl version command
• OperatorHub
• I don’t know

Environment

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

Eclipse Che Logs

Additional context

[l0rd]

I confirm I have seen the same problem this morning. That’s a blocker.

[l0rd]

👍 goo job, it works for me too.