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 server:deploy --version <..> doesn't work after changing projects structure in che-operator repository #20235

Closed
tolusha opened this issue Aug 2, 2021 · 0 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.
Milestone

Comments

@tolusha
Copy link
Contributor

tolusha commented Aug 2, 2021

Describe the bug

chectl server:deploy --version <..> doesn't work after changing projects structure in che-operator repository (after switching to a new operator sdk)

chectl tries to download templates from a deploy folder but now all templates are located in config folder.

 tolusha@fractal ~ $ chectl server:deploy --platform=minikube --installer operator --chenamespace eclipse-che --skip-kubernetes-health-check --version=7.34.0
› Current Kubernetes context: 'minikube'
  ✔ Verify Kubernetes API...OK
  ✔ 👀  Looking for an already existing Eclipse Che instance
    ✔ Verify if Eclipse Che is deployed into namespace "eclipse-che"...it is not
  ✔ Check versions compatibility... OK
  ✔ Download templates for version 7.34.0 ... OK
  ✔ ✈️  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.21.2.
    ✔ 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.99.100.nip.io.
    ✔ Checking minikube version... 1.22.0
    ↓ Check if cluster accessible [skipped]
  ✔ Following Eclipse Che logs
    ✔ Start following Operator logs...done
    ✔ Start following Eclipse Che Server logs...done
    ✔ Start following PostgreSQL logs...done
    ✔ Start following Keycloak logs...done
    ✔ Start following Plug-in Registry logs...done
    ✔ Start following Devfile Registry logs...done
    ✔ Start following Eclipse Che Dashboard logs...done
    ✔ Start following namespace events...done
 ›   Warning: Consider using the more reliable 'OLM' installer when deploying a stable release of Eclipse Che (--installer=olm).
  ❯ 🏃‍  Running the Eclipse Che operator
    ✔ Create Namespace (eclipse-che)...It already exists.
    ✖ Create ServiceAccount che-operator in namespace eclipse-che
      → ENOENT: no such file or directory, open '/home/tolusha/.cache/chectl/templates/7.34.0/che-operator/service_account.yaml'
      Read Roles and Bindings
      Creating Roles and Bindings
      Create CRD checlusters.org.eclipse.che
      Create backup and restore CRDs
      Waiting 5 seconds for the new Kubernetes resources to get flushed
      Create deployment che-operator in namespace eclipse-che
      Operator pod bootstrap
      Prepare Eclipse Che cluster CR
    Error: Command server:deploy failed. Error log: /home/tolusha/.cache/chectl/error.log.
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

1 participant