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.

Sign up for GitHub

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

Jump to bottom

Error installing eclipse che using chectl - FailedScheduling #17184

Closed
5 of 20 tasks
alohl669 opened this issue Jun 18, 2020 · 1 comment
Closed
5 of 20 tasks

Error installing eclipse che using chectl - FailedScheduling #17184

alohl669 opened this issue Jun 18, 2020 · 1 comment
Labels
area/chectl Issues related to chectl, the CLI of Che kind/bug Outline of a bug - must adhere to the bug report template. severity/P1 Has a major impact to usage or development of the system.

Comments

@alohl669
Copy link

alohl669 commented Jun 18, 2020 •
edited
Loading

Describe the bug

I've been trying to install Eclipse Che with minikube for a while and there is a point where I can't get ahead.

Che version

  • latest
  • nightly
  • other: please specify

Steps to reproduce

Unsing
chectl server:start --platform minikube
The error comes at this point:

 ❯ ✅  Post installation checklist
    ❯ PostgreSQL pod bootstrap
      ✔ scheduling...done.
      ✖ downloading images
        → ERR_TIMEOUT: Timeout set to pod wait timeout 300000

...

    Show important messages
 ›   Error: Error: ERR_TIMEOUT: Timeout set to pod wait timeout 300000
 ›   Installation failed, check logs in '/tmp/chectl-logs/1592471404435'

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)
minikube version: v1.11.0
commit: 57e2f55f47effe9ce396cea42a1e0eb4f611ebbd

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"
               }

QEMU emulator version 3.1.0 (Debian 1:3.1+dfsg-8+deb10u5)
Copyright (c) 2003-2018 Fabrice Bellard and the QEMU Project developers

$ kubectl get pods --all-namespaces
NAMESPACE     NAME                                        READY   STATUS      RESTARTS   AGE
kube-system   coredns-66bff467f8-h4zmz                    1/1     Running     0          32m
kube-system   coredns-66bff467f8-lxz6v                    1/1     Running     0          32m
kube-system   etcd-minikube                               1/1     Running     0          32m
kube-system   ingress-nginx-admission-create-dljvk        0/1     Completed   0          30m
kube-system   ingress-nginx-admission-patch-dzp6b         0/1     Completed   0          30m
kube-system   ingress-nginx-controller-7bb4c67d67-r56gj   1/1     Running     0          30m
kube-system   kube-apiserver-minikube                     1/1     Running     0          32m
kube-system   kube-controller-manager-minikube            1/1     Running     0          32m
kube-system   kube-proxy-57zvx                            1/1     Running     0          32m
kube-system   kube-scheduler-minikube                     1/1     Running     0          32m
kube-system   storage-provisioner                         1/1     Running     1          32m

Screenshots

imagen

Installation method

  • chectl
    chectl server:start --platform minikube
› Current Kubernetes context: 'minikube'
› 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
  ✔ ✈️  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.3.
    ✔ Verify if minikube ingress addon is enabled
    ✔ Enable minikube ingress addon
    ✔ Retrieving minikube IP and domain for ingress URLs...192.168.39.68.nip.io.
    ↓ Check if cluster accessible [skipped]
Eclipse Che logs will be available in '/tmp/chectl-logs/1592471404435'
  ✔ 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
 ›   Warning: Consider using the more reliable 'OLM' installer when deploying a stable release of Eclipse Che (--installer=olm).
 ›   Warning: Self-signed certificate is used, so "--self-signed-cert" option is required. Added automatically.
  ✔ 🏃‍  Running the Eclipse Che operator
    ✔ Copying operator resources...done.
    ✔ Create Namespace (che)...It already exists.
    ✔ Checking certificate... self-signed
    ✔ Create ServiceAccount che-operator in namespace che...done.
    ✔ Create Role che-operator in namespace che...done.
    ✔ Create ClusterRole che-operator...done.
    ✔ Create RoleBinding che-operator in namespace che...done.
    ✔ Create ClusterRoleBinding che-operator...done.
    ✔ Create CRD checlusters.org.eclipse.che...It already exists.
    ✔ Waiting 5 seconds for the new Kubernetes resources to get flushed...done.
    ✔ Create deployment che-operator in namespace che...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
        → ERR_TIMEOUT: Timeout set to pod wait timeout 300000
        starting
      Keycloak pod bootstrap
      Devfile registry pod bootstrap
      Plugin registry pod bootstrap
      Eclipse Che pod bootstrap
      Retrieving Eclipse Che server URL
      Eclipse Che status check
    Retrieving Keycloak admin credentials
    Retrieving Che self-signed CA certificate
    Show important messages
 ›   Error: Error: ERR_TIMEOUT: Timeout set to pod wait timeout 300000
 ›   Installation failed, check logs in '/tmp/chectl-logs/1592471404435'

Environment

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

Eclipse Che Logs

LAST SEEN   TYPE     REASON              OBJECT                    MESSAGE
0s          Normal   ScalingReplicaSet   deployment/che-operator   Scaled up replica set che-operator-7f7575f6fb to 1
0s          Normal   SuccessfulCreate    replicaset/che-operator-7f7575f6fb   Created pod: che-operator-7f7575f6fb-xjqg9
0s          Normal   Scheduled           pod/che-operator-7f7575f6fb-xjqg9    Successfully assigned che/che-operator-7f7575f6fb-xjqg9 to minikube
0s          Normal   Pulling             pod/che-operator-7f7575f6fb-xjqg9    Pulling image "quay.io/eclipse/che-operator:7.14.2"
0s          Normal   Pulled              pod/che-operator-7f7575f6fb-xjqg9    Successfully pulled image "quay.io/eclipse/che-operator:7.14.2"
0s          Normal   Created             pod/che-operator-7f7575f6fb-xjqg9    Created container che-operator
0s          Normal   Started             pod/che-operator-7f7575f6fb-xjqg9    Started container che-operator
0s          Normal   SuccessfulCreate    job/che-tls-job                      Created pod: che-tls-job-6pj8p
0s          Normal   Scheduled           pod/che-tls-job-6pj8p                Successfully assigned che/che-tls-job-6pj8p to minikube
0s          Normal   Pulling             pod/che-tls-job-6pj8p                Pulling image "quay.io/eclipse/che-tls-secret-creator:alpine-3029769"
0s          Normal   Pulled              pod/che-tls-job-6pj8p                Successfully pulled image "quay.io/eclipse/che-tls-secret-creator:alpine-3029769"
0s          Normal   Created             pod/che-tls-job-6pj8p                Created container che-tls-job-job-container
0s          Normal   Started             pod/che-tls-job-6pj8p                Started container che-tls-job-job-container
0s          Normal   Completed           job/che-tls-job                      Job completed
0s          Normal   ExternalProvisioning   persistentvolumeclaim/postgres-data   waiting for a volume to be created, either by external provisioner "k8s.io/minikube-hostpath" or manually created by system administrator
0s          Normal   ExternalProvisioning   persistentvolumeclaim/postgres-data   waiting for a volume to be created, either by external provisioner "k8s.io/minikube-hostpath" or manually created by system administrator
0s          Normal   ScalingReplicaSet      deployment/postgres                   Scaled up replica set postgres-59b797464c to 1
0s          Normal   SuccessfulCreate       replicaset/postgres-59b797464c        Created pod: postgres-59b797464c-vdfnl
0s          Warning   FailedScheduling       pod/postgres-59b797464c-vdfnl         running "VolumeBinding" filter plugin for pod "postgres-59b797464c-vdfnl": pod has unbound immediate PersistentVolumeClaims
0s          Warning   FailedScheduling       pod/postgres-59b797464c-vdfnl         running "VolumeBinding" filter plugin for pod "postgres-59b797464c-vdfnl": pod has unbound immediate PersistentVolumeClaims
0s          Normal    ExternalProvisioning   persistentvolumeclaim/postgres-data   waiting for a volume to be created, either by external provisioner "k8s.io/minikube-hostpath" or manually created by system administrator
0s          Normal    ExternalProvisioning   persistentvolumeclaim/postgres-data   waiting for a volume to be created, either by external provisioner "k8s.io/minikube-hostpath" or manually created by system administrator
0s          Normal    ExternalProvisioning   persistentvolumeclaim/postgres-data   waiting for a volume to be created, either by external provisioner "k8s.io/minikube-hostpath" or manually created by system administrator
0s          Normal    ExternalProvisioning   persistentvolumeclaim/postgres-data   waiting for a volume to be created, either by external provisioner "k8s.io/minikube-hostpath" or manually created by system administrator
0s          Warning   FailedScheduling       pod/postgres-59b797464c-vdfnl         running "VolumeBinding" filter plugin for pod "postgres-59b797464c-vdfnl": pod has unbound immediate PersistentVolumeClaims
0s          Normal    ExternalProvisioning   persistentvolumeclaim/postgres-data   waiting for a volume to be created, either by external provisioner "k8s.io/minikube-hostpath" or manually created by system administrator
0s          Normal    ExternalProvisioning   persistentvolumeclaim/postgres-data   waiting for a volume to be created, either by external provisioner "k8s.io/minikube-hostpath" or manually created by system administrator
0s          Normal    ExternalProvisioning   persistentvolumeclaim/postgres-data   waiting for a volume to be created, either by external provisioner "k8s.io/minikube-hostpath" or manually created by system administrator
0s          Normal    ExternalProvisioning   persistentvolumeclaim/postgres-data   waiting for a volume to be created, either by external provisioner "k8s.io/minikube-hostpath" or manually created by system administrator
0s          Normal    ExternalProvisioning   persistentvolumeclaim/postgres-data   waiting for a volume to be created, either by external provisioner "k8s.io/minikube-hostpath" or manually created by system administrator
0s          Normal    ExternalProvisioning   persistentvolumeclaim/postgres-data   waiting for a volume to be created, either by external provisioner "k8s.io/minikube-hostpath" or manually created by system administrator
0s          Warning   FailedScheduling       pod/postgres-59b797464c-vdfnl         running "VolumeBinding" filter plugin for pod "postgres-59b797464c-vdfnl": pod has unbound immediate PersistentVolumeClaims
0s          Normal    ExternalProvisioning   persistentvolumeclaim/postgres-data   waiting for a volume to be created, either by external provisioner "k8s.io/minikube-hostpath" or manually created by system administrator
0s          Normal    ExternalProvisioning   persistentvolumeclaim/postgres-data   waiting for a volume to be created, either by external provisioner "k8s.io/minikube-hostpath" or manually created by system administrator
0s          Normal    ExternalProvisioning   persistentvolumeclaim/postgres-data   waiting for a volume to be created, either by external provisioner "k8s.io/minikube-hostpath" or manually created by system administrator
0s          Normal    ExternalProvisioning   persistentvolumeclaim/postgres-data   waiting for a volume to be created, either by external provisioner "k8s.io/minikube-hostpath" or manually created by system administrator
0s          Normal    ExternalProvisioning   persistentvolumeclaim/postgres-data   waiting for a volume to be created, either by external provisioner "k8s.io/minikube-hostpath" or manually created by system administrator
0s          Normal    ExternalProvisioning   persistentvolumeclaim/postgres-data   waiting for a volume to be created, either by external provisioner "k8s.io/minikube-hostpath" or manually created by system administrator
0s          Warning   FailedScheduling       pod/postgres-59b797464c-vdfnl         running "VolumeBinding" filter plugin for pod "postgres-59b797464c-vdfnl": pod has unbound immediate PersistentVolumeClaims
0s          Normal    ExternalProvisioning   persistentvolumeclaim/postgres-data   waiting for a volume to be created, either by external provisioner "k8s.io/minikube-hostpath" or manually created by system administrator
0s          Normal    ExternalProvisioning   persistentvolumeclaim/postgres-data   waiting for a volume to be created, either by external provisioner "k8s.io/minikube-hostpath" or manually created by system administrator
0s          Normal    ExternalProvisioning   persistentvolumeclaim/postgres-data   waiting for a volume to be created, either by external provisioner "k8s.io/minikube-hostpath" or manually created by system administrator
0s          Normal    ExternalProvisioning   persistentvolumeclaim/postgres-data   waiting for a volume to be created, either by external provisioner "k8s.io/minikube-hostpath" or manually created by system administrator
0s          Normal    ExternalProvisioning   persistentvolumeclaim/postgres-data   waiting for a volume to be created, either by external provisioner "k8s.io/minikube-hostpath" or manually created by system administrator
0s          Normal    ExternalProvisioning   persistentvolumeclaim/postgres-data   waiting for a volume to be created, either by external provisioner "k8s.io/minikube-hostpath" or manually created by system administrator
0s          Warning   FailedScheduling       pod/postgres-59b797464c-vdfnl         running "VolumeBinding" filter plugin for pod "postgres-59b797464c-vdfnl": pod has unbound immediate PersistentVolumeClaims
0s          Normal    ExternalProvisioning   persistentvolumeclaim/postgres-data   waiting for a volume to be created, either by external provisioner "k8s.io/minikube-hostpath" or manually created by system administrator
0s          Normal    ExternalProvisioning   persistentvolumeclaim/postgres-data   waiting for a volume to be created, either by external provisioner "k8s.io/minikube-hostpath" or manually created by system administrator

Additional context

I currently have a minikube installed with kvm2. The machine that runs it is a virtual machine with nested virtualization enabled. Following the advice of the documentation of che i runs minikube with at least 4GB of ram(the virtual machine has at least 6).
This is the list of versions I have installed

Distributor ID: Debian
Description:    Debian GNU/Linux 10 (buster)
Release:        10
Codename:       buster

minikube version: v1.11.0
commit: 57e2f55f47effe9ce396cea42a1e0eb4f611ebbd

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"
               }

Eclipse Che CLI

VERSION
  chectl/7.14.2 linux-x64 node-v10.21.0

QEMU emulator version 3.1.0 (Debian 1:3.1+dfsg-8+deb10u5)
Copyright (c) 2003-2018 Fabrice Bellard and the QEMU Project developers
@alohl669 alohl669 added the kind/bug Outline of a bug - must adhere to the bug report template. label Jun 18, 2020
@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 Jun 18, 2020
@rhopp rhopp added area/chectl Issues related to chectl, the CLI of Che severity/P1 Has a major impact to usage or development of the system. and removed status/need-triage An issue that needs to be prioritized by the curator responsible for the triage. See https://github. labels Jun 19, 2020
@mmorhun
Copy link
Contributor

mmorhun commented Jun 25, 2020

Same problem as in #17142 and fixed by che-incubator/chectl#752

@mmorhun mmorhun closed this as completed Jun 25, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
area/chectl Issues related to chectl, the CLI of Che kind/bug Outline of a bug - must adhere to the bug report template. severity/P1 Has a major impact to usage or development of the system.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@rhopp @mmorhun @alohl669 @che-bot