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.

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

Che installation fails on Minikube 1.13.1 #17952

Closed
mmorhun opened this issue Sep 24, 2020 · 9 comments
Closed

Che installation fails on Minikube 1.13.1 #17952

mmorhun opened this issue Sep 24, 2020 · 9 comments
Assignees
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.
Milestone

Comments

@mmorhun
Copy link
Contributor

mmorhun commented Sep 24, 2020

Describe the bug

If try to install Eclipse Che on latest (1.13.1) Minikube, the installation fails:

  ✔ 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.19.2.
    ✔ Verify if minikube ingress addon is enabled
    ✖ Enable minikube ingress addon
      → * Verifying ingress addon...
      Retrieving minikube IP and domain for ingress URLs
      Checking minikube version
      Check if cluster accessible
 ›   Error: Error: Command timed out after 18000 milliseconds: minikube addons enable ingress
 ›   Timed out
 ›   * Verifying ingress addon...
 ›   Installation failed. There are no available logs.

Che version

nightly

Steps to reproduce

Try to install Eclispe Che on Minikube 1.13.1

Expected behavior

Installation is successful

Runtime

Minikube 1.13.1

Installation method

chectl

@mmorhun mmorhun added kind/bug Outline of a bug - must adhere to the bug report template. severity/blocker Causes system to crash and be non-recoverable or prevents Che developers from working on Che code. labels Sep 24, 2020
@mmorhun mmorhun self-assigned this Sep 24, 2020
@benoitf
Copy link
Contributor

benoitf commented Sep 24, 2020

I think chectl should not start minikube and try to enable ingresses by itself. Just report that ingress addon is not there and that minikube should be launched with --addons=ingress
(to avoid such errors)

@mmorhun
Copy link
Contributor Author

mmorhun commented Sep 24, 2020

@benoitf yes, but not all users know about that.

@benoitf
Copy link
Contributor

benoitf commented Sep 24, 2020

there is also some incompatibility on macos with minkube and ingresses. For example it's saying that ingress addon can't be enabled (depending on the driver) so even extending timeout will fail anyway

@benoitf
Copy link
Contributor

benoitf commented Sep 24, 2020

@benoitf yes, but not all users know about that.

chectl should print a nice message.

@mmorhun
Copy link
Contributor Author

mmorhun commented Sep 24, 2020

chectl should print a nice message.

chectl enables it automatically if it wasn't.

@benoitf
Copy link
Contributor

benoitf commented Sep 24, 2020

what i'm saying is that chectl can't do it automatically on minikube/macos with default minikube settings

@l0rd
Copy link
Contributor

l0rd commented Sep 24, 2020

Starting with minikube 1.12 docker is the default minikube driver but the ingress add-on doesn't work with the docker driver. The command minikube start --memory=4096 is not enough anymore on fresh installations.

What I would propose is:

  1. Fix documentation and code to minikube start --memory=4096 --vm=true && minikube addons enable ingress on mac and windows
  2. Update code to avoid starting minikube but providing explicit instruction to install / run / enable ingress for minikube based on the platform.

@benoitf
Copy link
Contributor

benoitf commented Sep 24, 2020

For the documentation,
minikube start --memory=4096 --vm=true && minikube addons enable ingress
can be replaced by
minikube start --memory=4096 --vm=true --addons=ingress

@mmorhun
Copy link
Contributor Author

mmorhun commented Sep 24, 2020

what i'm saying is that chectl can't do it automatically on minikube/macos with default minikube settings

@benoitf I see. I tested it on Fedora and everything was working fine.

@tolusha tolusha added severity/P1 Has a major impact to usage or development of the system. area/chectl Issues related to chectl, the CLI of Che and removed severity/blocker Causes system to crash and be non-recoverable or prevents Che developers from working on Che code. labels Sep 25, 2020
@mmorhun mmorhun closed this as completed Sep 28, 2020
@tolusha tolusha mentioned this issue Sep 28, 2020
48 tasks
@tolusha tolusha added this to the 7.20 milestone Sep 28, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to 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.
Projects
None yet
Development

No branches or pull requests

4 participants