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-operator] Operator installer failed being run by chectl with default value of che version #16072

Closed
4 of 23 tasks
dmytro-ndp opened this issue Feb 19, 2020 · 5 comments
Closed
4 of 23 tasks
Assignees
Labels
area/che-operator Issues and PRs related to Eclipse Che Kubernetes Operator area/qe 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.
Milestone

Comments

@dmytro-ndp
Copy link
Contributor

dmytro-ndp commented Feb 19, 2020

Describe the bug

There was che-operator deployment error when it was tried to install Eclipse Che on minikube by command:

chectl server:start --k8spodreadytimeout=180000 --installer=operator --listr-renderer=verbose --platform=minikube --che-operator-cr-yaml=custom-resource.yaml

Che operator pod logs:

time="2020-02-19T01:39:04Z" level=fatal msg="Failed to initialize default value: 'CHE_VERSION'. Environment variable with default value was not found."

 Chectl logs  
[10:55:16] Verify Kubernetes API [started]
[10:55:16] Verify Kubernetes API...OK [title changed]
[10:55:16] Verify Kubernetes API...OK [completed]
[10:55:16] 👀  Looking for an already existing Eclipse Che instance [started]
[10:55:16] Verify if Eclipse Che is deployed into namespace "che" [started]
[10:55:16] Verify if Eclipse Che is deployed into namespace "che"...it is not [title changed]
[10:55:16] Verify if Eclipse Che is deployed into namespace "che"...it is not [completed]
[10:55:16] 👀  Looking for an already existing Eclipse Che instance [completed]
[10:55:16] ✈️  Minikube preflight checklist [started]
[10:55:16] Verify if kubectl is installed [started]
[10:55:16] Verify if kubectl is installed [completed]
[10:55:16] Verify if minikube is installed [started]
[10:55:16] Verify if minikube is installed [completed]
[10:55:16] Verify if minikube is running [started]
[10:55:16] Verify if minikube is running [completed]
[10:55:16] Start minikube [started]
[10:55:16] Start minikube [skipped]
[10:55:16] → Minikube is already running.
[10:55:16] Check Kubernetes version [started]
[10:55:17] Check Kubernetes version: Found v1.14.3. [title changed]
[10:55:17] Check Kubernetes version: Found v1.14.3. [completed]
[10:55:17] Verify if minikube ingress addon is enabled [started]
[10:55:17] Verify if minikube ingress addon is enabled [completed]
[10:55:17] Enable minikube ingress addon [started]
[10:55:17] Enable minikube ingress addon [skipped]
[10:55:17] → Ingress addon is already enabled.
[10:55:17] Retrieving minikube IP and domain for ingress URLs [started]
[10:55:17] Retrieving minikube IP and domain for ingress URLs...10.0.101.55.nip.io. [title changed]
[10:55:17] Retrieving minikube IP and domain for ingress URLs...10.0.101.55.nip.io. [completed]
[10:55:17] ✈️  Minikube preflight checklist [completed]
Eclipse Che logs will be available in '/tmp/chectl-logs/1582041316045'
[10:55:17] Start following logs [started]
[10:55:17] Start following Eclipse Che logs [started]
[10:55:17] Start following Eclipse Che logs...done [title changed]
[10:55:17] Start following Eclipse Che logs...done [completed]
[10:55:17] Start following Postgres logs [started]
[10:55:17] Start following Postgres logs...done [title changed]
[10:55:17] Start following Postgres logs...done [completed]
[10:55:17] Start following Keycloak logs [started]
[10:55:17] Start following Keycloak logs...done [title changed]
[10:55:17] Start following Keycloak logs...done [completed]
[10:55:17] Start following Plugin registry logs [started]
[10:55:17] Start following Plugin registry logs...done [title changed]
[10:55:17] Start following Plugin registry logs...done [completed]
[10:55:17] Start following Devfile registry logs [started]
[10:55:17] Start following Devfile registry logs...done [title changed]
[10:55:17] Start following Devfile registry logs...done [completed]
[10:55:17] Start following logs [completed]
[10:55:17] Start following events [started]
[10:55:17] Start following namespace events [started]
[10:55:17] Start following namespace events...done [title changed]
[10:55:17] Start following namespace events...done [completed]
[10:55:17] Start following events [completed]
[10:55:17] 🏃‍  Running the Che Operator [started]
 ›   Warning: Eclipse Che will be deployed in Multi-User mode as 'operator' 
 ›   installer supports only that mode.
[10:55:17] Copying operator resources [started]
[10:55:17] Copying operator resources...done. [title changed]
[10:55:17] Copying operator resources...done. [completed]
[10:55:17] Create Namespace (che) [started]
[10:55:17] Create Namespace (che)...done. [title changed]
[10:55:17] Create Namespace (che)...done. [completed]
[10:55:17] Create ServiceAccount che-operator in namespace che [started]
[10:55:17] Create ServiceAccount che-operator in namespace che...done. [title changed]
[10:55:17] Create ServiceAccount che-operator in namespace che...done. [completed]
[10:55:17] Create Role che-operator in namespace che [started]
[10:55:17] Create Role che-operator in namespace che...done. [title changed]
[10:55:17] Create Role che-operator in namespace che...done. [completed]
[10:55:17] Create ClusterRole che-operator [started]
[10:55:17] Create ClusterRole che-operator...done. [title changed]
[10:55:17] Create ClusterRole che-operator...done. [completed]
[10:55:17] Create RoleBinding che-operator in namespace che [started]
[10:55:17] Create RoleBinding che-operator in namespace che...done. [title changed]
[10:55:17] Create RoleBinding che-operator in namespace che...done. [completed]
[10:55:17] Create ClusterRoleBinding che-operator [started]
[10:55:17] Create ClusterRoleBinding che-operator...done. [title changed]
[10:55:17] Create ClusterRoleBinding che-operator...done. [completed]
[10:55:17] Create CRD checlusters.org.eclipse.che [started]
[10:55:17] Create CRD checlusters.org.eclipse.che...done. [title changed]
[10:55:17] Create CRD checlusters.org.eclipse.che...done. [completed]
[10:55:17] Waiting 5 seconds for the new Kubernetes resources to get flushed [started]
[10:55:22] Waiting 5 seconds for the new Kubernetes resources to get flushed...done. [title changed]
[10:55:22] Waiting 5 seconds for the new Kubernetes resources to get flushed...done. [completed]
[10:55:22] Create deployment che-operator in namespace che [started]
[10:55:22] Create deployment che-operator in namespace che...done. [title changed]
[10:55:22] Create deployment che-operator in namespace che...done. [completed]
[10:55:22] Create Eclipse Che Cluster eclipse-che in namespace che [started]
[10:55:22] Create Eclipse Che Cluster eclipse-che in namespace che...done. [title changed]
[10:55:22] Create Eclipse Che Cluster eclipse-che in namespace che...done. [completed]
[10:55:22] 🏃‍  Running the Che Operator [completed]
[10:55:22] ✅  Post installation checklist [started]
[10:55:22] PostgreSQL pod bootstrap [started]
[10:55:22] scheduling [started]
[11:00:27] scheduling [failed]
[11:00:27] → ERR_TIMEOUT: Timeout set to pod wait timeout 300000. podExist: false, currentPhase: undefined
[11:00:27] PostgreSQL pod bootstrap [failed]
[11:00:27] → ERR_TIMEOUT: Timeout set to pod wait timeout 300000. podExist: false, currentPhase: undefined
[11:00:27] ✅  Post installation checklist [failed]
[11:00:27] → ERR_TIMEOUT: Timeout set to pod wait timeout 300000. podExist: false, currentPhase: undefined
 ›   Error: Error: ERR_TIMEOUT: Timeout set to pod wait timeout 300000. 
 ›   podExist: false, currentPhase: undefined
 ›   Installation failed, check logs in '/tmp/chectl-logs/1582041316045'
 

custom-resource.yaml content: https://gist.github.com/dmytro-ndp/91ad3f3c61fba6fbd939d21d585af682

Related commit

eclipse-che/che-operator@e9c5d3f

Che version

  • latest
  • nightly
  • other: please specify

Steps to reproduce

  1. Install minikube 1.1.1.
  2. Download chectl from next channel.
  3. Execute the command:
chectl server:start --k8spodreadytimeout=180000 --installer=operator --listr-renderer=verbose --platform=minikube --che-operator-cr-yaml=custom-resource.yaml

Expected behavior

chectl installs Eclipse Che of nightly version

Runtime

  • kubernetes (include output of kubectl version)
  • Openshift (include output of oc version)
  • minikube 1.1.1 (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)

Installation method

  • chectl:next with operator installer: chectl/0.0.20200218-next.3cc1458 linux-x64 node-v10.19.0
  • che-operator
  • minishift-addon
  • I don't know

Environment

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

Additional context

It affects Eclipse Che / Che-Theia PR check.

@dmytro-ndp dmytro-ndp 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. area/che-operator Issues and PRs related to Eclipse Che Kubernetes Operator area/qe labels Feb 19, 2020
@tolusha
Copy link
Contributor

tolusha commented Feb 19, 2020

Pls attach CR file

@dmytro-ndp
Copy link
Contributor Author

@tolusha
Copy link
Contributor

tolusha commented Feb 19, 2020

chectl released with dependencies on latest che and che-operator templates.

@tolusha tolusha closed this as completed Feb 19, 2020
@tolusha tolusha mentioned this issue Feb 19, 2020
46 tasks
@tolusha tolusha added this to the 7.10.0 milestone Feb 28, 2020
@nickboldt
Copy link
Contributor

nickboldt commented Mar 2, 2020

Was this fix backported to 7.9.x branch? I'm wondering how it was done (I don't see a linked PR).

Was it this?

eclipse-che/che-operator@b001254

It would be awesome if the inline error message didn't just say it's required but helped me find it from https://github.com/operator-framework/operator-sdk/releases/tag/v0.10.0

I'm curious why we require ONLY 0.10.0 when there's a 0.10.1 bugfix release, plus several newer releases like 0.15.2.

Well, anyway I downloaded 0.10.0 to get past the above problem, but now:

$➔ ./olm/update-cr-crd-files.sh 
FATA[0000] must run command in project root dir: project structure requires build/Dockerfile 

There's no build folder folder inside che-operator and the only Dockerfile is in the root.

So how do I use this?

nickboldt added a commit to eclipse-che/che-operator that referenced this issue Mar 2, 2020
…ating new file olm/update-cr-crd-files.sh and updating +x perms on all *.sh files

Change-Id: I30b0d7fa762c81f16a3729a5aa571bf2d477e348
Signed-off-by: nickboldt <[email protected]>
@tolusha
Copy link
Contributor

tolusha commented Mar 3, 2020

@nickboldt
#16206
Create build directory in the root of the project and copy Dockerfile there.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/che-operator Issues and PRs related to Eclipse Che Kubernetes Operator area/qe 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.
Projects
None yet
Development

No branches or pull requests

3 participants