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

[chectl] Installation of Eclipse Che 7.10.0.RC with custom templates folder using helm chart installer failed on minikube #16338

Closed
4 of 23 tasks
dmytro-ndp opened this issue Mar 12, 2020 · 3 comments
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

@dmytro-ndp
Copy link
Contributor

Describe the bug

Installation of Eclipse Che 7.10.0.RC with helm chart installer failed on minikube

/usr/local/bin/chectl server:start --k8spodreadytimeout=180000 -t=/mnt/hudson_workspace/workspace/Single-Che-pre-release-check-E2E-Happy-path-tests-against-K8S/deploy/ --platform=minikube --listr-renderer=verbose --skip-version-check --self-signed-cert --cheimage=eclipse/che-server:rc

14:09:23 [08:09:23] Deploy cert-manager [started]
14:09:23 [08:09:23] Deploy cert-manager [failed]
14:09:23 [08:09:23] → Command failed with exit code 1: kubectl apply -f /mnt/hudson_workspace/workspace/Single-Che-pre-release-check-E2E-Happy-path-tests-against-K8S/installers/cert-manager.yml --validate=false
14:09:23 error: the path "/mnt/hudson_workspace/workspace/Single-Che-pre-release-check-E2E-Happy-path-tests-against-K8S/installers/cert-manager.yml" does not exist
14:09:23 [08:09:23] Check Eclipse Che TLS certificate...going to generate self-signed one [failed]
14:09:23 [08:09:23] → Command failed with exit code 1: kubectl apply -f /mnt/hudson_workspace/workspace/Single-Che-pre-release-check-E2E-Happy-path-tests-against-K8S/installers/cert-manager.yml --validate=false
14:09:23 error: the path "/mnt/hudson_workspace/workspace/Single-Che-pre-release-check-E2E-Happy-path-tests-against-K8S/installers/cert-manager.yml" does not exist
14:09:23 [08:09:23] 🏃‍  Running Helm to install Eclipse Che [failed]
14:09:23 [08:09:23] → Command failed with exit code 1: kubectl apply -f /mnt/hudson_workspace/workspace/Single-Che-pre-release-check-E2E-Happy-path-tests-against-K8S/installers/cert-manager.yml --validate=false
14:09:23 error: the path "/mnt/hudson_workspace/workspace/Single-Che-pre-release-check-E2E-Happy-path-tests-against-K8S/installers/cert-manager.yml" does not exist
14:09:23  ›   Error: Error: Command failed with exit code 1: kubectl apply -f 
14:09:23  ›   /mnt/hudson_workspace/workspace/Single-Che-pre-release-check-E2E-Happy-pat
14:09:23  ›   h-tests-against-K8S/installers/cert-manager.yml --validate=false
14:09:23  ›   error: the path 
14:09:23  ›   "/mnt/hudson_workspace/workspace/Single-Che-pre-release-check-E2E-Happy-pa
14:09:23  ›   th-tests-against-K8S/installers/cert-manager.yml" does not exist
14:09:23  ›   Installation failed, check logs in '/tmp/chectl-logs/1584014962469'
14:09:23 Build step 'Execute shell' marked build as failure
14:09:24 Run condition [Always] enabling perform for step [[Execute Scripts]]
14:09:24 [PostBuildScript] - Executing post build scripts.

Possible reason

there are wrong container image tags (empty or 7.11.0) in Eclipse Che 7.10.0.RC helm charts: 1eaeb83#diff-38275c40bc918188a5eedbe0d3940b8d

Che version

  • latest
  • nightly
  • other: 7.10.0.RC

Runtime

  • kubernetes (include output of kubectl version)
  • Openshift (include output of oc version)
  • minikube 1.1.1
  • minishift (include output of minishift version and oc version)
  • docker-desktop + K8S (include output of docker version and kubectl version)
  • other: (please specify)

Installation method

Environment

  • my computer
    • Windows
    • Linux
    • macOS
  • Cloud
    • Amazon
    • Azure
    • GCE
    • other (please specify)
  • other: CRW CCI
@dmytro-ndp dmytro-ndp added kind/bug Outline of a bug - must adhere to the bug report template. area/chectl Issues related to chectl, the CLI of Che labels Mar 12, 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 Mar 12, 2020
@dmytro-ndp dmytro-ndp mentioned this issue Mar 12, 2020
17 tasks
@mmorhun
Copy link
Contributor

mmorhun commented Mar 12, 2020

To workaround the issue create directory installers near templates folder (on the same level) and put file cert-manager.yaml in it. (You may find this file in chectl repository under installers directory).
I think I will be able to fix this problem after next cert-manager release.

@mmorhun mmorhun changed the title [chectl] Installation of Eclipse Che 7.10.0.RC with helm chart installer failed on minikube [chectl] Installation of Eclipse Che 7.10.0.RC with custom templates folder using helm chart installer failed on minikube Mar 12, 2020
@dmytro-ndp
Copy link
Contributor Author

dmytro-ndp commented Mar 12, 2020

@mmorhun: thanks for explanation.
Did you mean to put che/deploy/cert-manager/che-certificate.yml file into che/deploy/kubernetes/installers directory?


An update:
we need to put https://raw.githubusercontent.com/che-incubator/chectl/master/installers/cert-manager.yml into the che/installers directory

@tolusha tolusha added the severity/P1 Has a major impact to usage or development of the system. label Mar 13, 2020
@tolusha tolusha added this to the Backlog - Deploy milestone Mar 13, 2020
@tolusha tolusha removed the status/need-triage An issue that needs to be prioritized by the curator responsible for the triage. See https://github. label Mar 13, 2020
@dmytro-ndp
Copy link
Contributor Author

Workaround does work.

@tolusha tolusha removed this from the Backlog - Deploy milestone Mar 17, 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