Get pods by selector "app.kubernetes.io/name=cert-manager" returned a pod without a status.condition of type "Ready"

[gnoejuan]

Describe the bug

chectl server:start -b 192.168.1.43 -p k8s from Laptop. I have k3os installed on a server on the same LAN. Kubectl was set up using the instuctions found here: https://opensource.com/article/20/3/kubernetes-raspberry-pi-k3s

It'd be annoying to have to ssh to the master node to run kubectl anytime we wanted to inspect or modify our cluster. So, we want to put kubectl on our PC. But first, let's get the configuration information we need from our master node. Ssh into kmaster and run:

sudo cat /etc/rancher/k3s/k3s.yaml

Copy this configuration information and return to your PC. Make a directory for the config:

mkdir ~/.kube

Save the copied configuration as ~/.kube/config. Now edit the file and change the line:

server: https://localhost:6443

to be:

server: https://kmaster:6443

For security purpose, limit the file's read/write permissions to just yourself:

chmod 600 ~/.kube/config

I am greeted with the following:

Set current context to 'default'
  ✔ Verify Kubernetes API...OK
  ✔ 👀  Looking for an already existing Eclipse Che instance
    ✔ Verify if Eclipse Che is deployed into namespace "che"...it is not
  ✔ ✈  Kubernetes preflight checklist
    ✔ Verify if kubectl is installed
    ✔ Verify remote kubernetes status...done.
    ✔ Check Kubernetes version: Found v1.17.5+k3s1.
    ✔ Verify domain is set...set to 192.168.1.43.
    ↓ Check if cluster accessible [skipped]
Eclipse Che logs will be available in '/tmp/chectl-logs/1590266338519'
  ✔ 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
  ❯ 🏃  Running Helm to install Eclipse Che
    ✔ Verify if helm is installed
    ✔ Check Helm Version: Found v3.2.1+gfe51cd1
    ✔ 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
        → Get pods by selector "app.kubernetes.io/name=cert-manager" returned a pod without a status.condition of type "Ready"
        Check Cert Manager CA certificate
        Set up Eclipse Che certificates issuer
        Request self-signed certificate
        Wait for self-signed certificate
        Add local Eclipse Che CA certificate into browser
      Check Cluster Role Binding
      Preparing Eclipse Che Helm Chart
      Updating Helm Chart dependencies
      Deploying Eclipse Che Helm Chart
 ›   Error: Error: Get pods by selector "app.kubernetes.io/name=cert-manager" returned a pod without a status.condition of type "Ready"
 ›   Installation failed, check logs in '/tmp/chectl-logs/1590266338519'

On second Run:

❯ 🏃  Running Helm to install Eclipse Che
    ✔ Verify if helm is installed
    ✔ Check Helm Version: Found v3.2.1+gfe51cd1
    ✔ Create Namespace (che)...does already exist.
    ❯ Check Eclipse Che TLS certificate...going to generate self-signed one
      ✔ Check Cert Manager deployment...already deployed
      ✔ Wait for cert-manager...ready
      ✖ Check Cert Manager CA certificate...generating new one
        → Failed to generate self-signed CA certificate: generating job failed.

On third run, I'm getting timeouts downloading the images, but that's a problem with my ISP.

The directories that chectl printed for logs were empty

I'm about to head to work and I didn't want to lose the terminal output

Che version

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

Steps to reproduce

Expected behavior

Runtime

• [ x ] kubernetes (include output of kubectl version)
  Server

k3os-12376 [~]$ kubectl version
Client Version: version.Info{Major:"1", Minor:"17", GitVersion:"v1.17.5+k3s1", GitCommit:"58ebdb2a2ec5318ca40649eb7bd31679cb679f71", GitTreeState:"clean", BuildDate:"2020-05-06T23:43:23Z", GoVersion:"go1.13.8", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"17", GitVersion:"v1.17.5+k3s1", GitCommit:"58ebdb2a2ec5318ca40649eb7bd31679cb679f71", GitTreeState:"clean", BuildDate:"2020-05-06T23:43:23Z", GoVersion:"go1.13.8", Compiler:"gc", Platform:"linux/amd64"}

Laptop

C:\home\charlesrod> kubectl version
Client Version: version.Info{Major:"1", Minor:"18", GitVersion:"v1.18.3", GitCommit:"2e7996e3e2712684bc73f0dec0200d64eec7fe40", GitTreeState:"clean", BuildDate:"2020-05-20T12:52:00Z", GoVersion:"go1.13.9", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"17", GitVersion:"v1.17.5+k3s1", GitCommit:"58ebdb2a2ec5318ca40649eb7bd31679cb679f71", GitTreeState:"clean", BuildDate:"2020-05-06T23:43:23Z", GoVersion:"go1.13.8", Compiler:"gc", Platform:"linux/amd64"}

• 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

C:\tmp\chectl-logs\1590284888324\che> chectl --version
chectl/7.13.1 linux-x64 node-v10.20.1

• OperatorHub
• I don't know

Environment

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

Eclipse Che Logs

Additional context

[tolusha]

@gnoejuan
Thank you for report

 Wait for cert-manager
        → Get pods by selector "app.kubernetes.io/name=cert-manager" returned a pod without a status.condition of type "Ready"

I got the problem.

[tolusha]

fixed in che-incubator/chectl@53b4f98