Happy path test on CRW CI failed on Start Che because chectl:next doesn't support minikube 1.1.1
See original GitHub issueDescribe the bug
chectl/0.0.20210422-next.07f7844 failed to execute “server:deploy” command on minikube 1.1.1:
chectl server:deploy --k8spodreadytimeout=600000 --k8spodwaittimeout=600000 --k8spoddownloadimagetimeout=600000 --listr-renderer=verbose --platform=minikube --che-operator-cr-patch-yaml=custom-resource-patch.yaml --telemetry=off --chenamespace=eclipse-che
where custom-resource-patch.yaml:
spec:
server:
cheImage: 'quay.io/crw_pr/che-server'
cheImageTag: '19521'
customCheProperties:
CHE_LIMITS_USER_WORKSPACES_RUN_COUNT: '-1'
CHE_WORKSPACE_SIDECAR_IMAGE__PULL__POLICY: IfNotPresent
CHE_WORKSPACE_PLUGIN__BROKER_PULL__POLICY: IfNotPresent
CHE_INFRA_KUBERNETES_WORKSPACE_START_TIMEOUT_MIN: '12'
auth:
updateAdminPassword: false
chectl logs:
(node:10864) Warning: Setting the NODE_TLS_REJECT_UNAUTHORIZED environment variable to '0' makes TLS connections and HTTPS requests insecure by disabling certificate verification.
› Installer type is set to: 'operator'
[06:05:50] Verify Kubernetes API [started]
› Current Kubernetes context: 'minikube'
[06:05:50] Verify Kubernetes API...OK [title changed]
[06:05:50] Verify Kubernetes API...OK [completed]
[06:05:50] 👀 Looking for an already existing Eclipse Che instance [started]
[06:05:50] Verify if Eclipse Che is deployed into namespace "eclipse-che" [started]
[06:05:50] Verify if Eclipse Che is deployed into namespace "eclipse-che"...it is not [title changed]
[06:05:50] Verify if Eclipse Che is deployed into namespace "eclipse-che"...it is not [completed]
[06:05:50] 👀 Looking for an already existing Eclipse Che instance [completed]
[06:05:50] ✈️ Minikube preflight checklist [started]
[06:05:50] Verify if kubectl is installed [started]
[06:05:50] Verify if kubectl is installed [completed]
[06:05:50] Verify if minikube is installed [started]
[06:05:50] Verify if minikube is installed [completed]
[06:05:50] Verify if minikube is running [started]
[06:05:50] Verify if minikube is running [completed]
[06:05:50] Start minikube [started]
[06:05:50] Start minikube [skipped]
[06:05:50] → Minikube is already running.
[06:05:50] Check Kubernetes version [started]
[06:05:50] Check Kubernetes version: Found v1.14.3. [title changed]
[06:05:50] Check Kubernetes version: Found v1.14.3. [completed]
[06:05:50] Verify if minikube ingress addon is enabled [started]
[06:05:50] Verify if minikube ingress addon is enabled [completed]
[06:05:50] Enable minikube ingress addon [started]
[06:05:50] Enable minikube ingress addon [skipped]
[06:05:50] → Ingress addon is already enabled.
[06:05:50] Retrieving minikube IP and domain for ingress URLs [started]
[06:05:50] Retrieving minikube IP and domain for ingress URLs...10.0.206.207.nip.io. [title changed]
[06:05:50] Retrieving minikube IP and domain for ingress URLs...10.0.206.207.nip.io. [completed]
[06:05:50] Checking minikube version [started]
[06:05:50] Checking minikube version... 1.1.1 [title changed]
[06:05:50] Checking minikube version... 1.1.1 [completed]
[06:05:50] Check if cluster accessible [started]
[06:05:50] Check if cluster accessible [skipped]
[06:05:50] ✈️ Minikube preflight checklist [completed]
[06:05:50] Following Eclipse Che logs [started]
[06:05:50] Start following Operator logs [started]
[06:05:50] Start following Operator logs...done [title changed]
[06:05:50] Start following Operator logs...done [completed]
[06:05:50] Start following Eclipse Che server logs [started]
[06:05:50] Start following Eclipse Che server logs...done [title changed]
[06:05:50] Start following Eclipse Che server logs...done [completed]
[06:05:50] Start following Postgres logs [started]
[06:05:50] Start following Postgres logs...done [title changed]
[06:05:50] Start following Postgres logs...done [completed]
[06:05:50] Start following Keycloak logs [started]
[06:05:50] Start following Keycloak logs...done [title changed]
[06:05:50] Start following Keycloak logs...done [completed]
[06:05:50] Start following Plugin registry logs [started]
[06:05:50] Start following Plugin registry logs...done [title changed]
[06:05:50] Start following Plugin registry logs...done [completed]
[06:05:50] Start following Devfile registry logs [started]
[06:05:50] Start following Devfile registry logs...done [title changed]
[06:05:50] Start following Devfile registry logs...done [completed]
[06:05:50] Start following namespace events [started]
[06:05:50] Start following namespace events...done [title changed]
[06:05:50] Start following namespace events...done [completed]
[06:05:50] Following Eclipse Che logs [completed]
[06:05:51] 🏃 Running the Eclipse Che operator [started]
[06:05:51] Create Namespace (eclipse-che) [started]
[06:05:51] Create Namespace (eclipse-che)...Done. [title changed]
[06:05:51] Create Namespace (eclipse-che)...Done. [completed]
[06:05:51] Create ServiceAccount che-operator in namespace eclipse-che [started]
[06:05:51] Create ServiceAccount che-operator in namespace eclipse-che...done. [title changed]
[06:05:51] Create ServiceAccount che-operator in namespace eclipse-che...done. [completed]
[06:05:51] Read Roles and Bindings [started]
[06:05:51] Read Roles and Bindings...done. [title changed]
[06:05:51] Read Roles and Bindings...done. [completed]
[06:05:51] Creating Roles and Bindings [started]
[06:05:51] Creating Roles and Bindings...done. [title changed]
[06:05:51] Creating Roles and Bindings...done. [completed]
[06:05:51] Create CRD checlusters.org.eclipse.che [started]
[06:05:51] Create CRD checlusters.org.eclipse.che [failed]
[06:05:51] → the server could not find the requested resource
[06:05:51] 🏃 Running the Eclipse Che operator [failed]
[06:05:51] → the server could not find the requested resource
› Error: Error: the server could not find the requested resource
› Command server:deploy failed. Error log:
› /home/hudson/.cache/chectl/error.log
Che version
- latest
- nightly
- other: please specify
Steps to reproduce
Expected behavior
Runtime
- kubernetes (include output of
kubectl version
) - Openshift (include output of
oc version
) - minikube 1.1.1 (include output of
minikube version
andkubectl version
) - minishift (include output of
minishift version
andoc version
) - docker-desktop + K8S (include output of
docker version
andkubectl version
) - other: (please specify)
Screenshots
Installation method
- chectl/0.0.20210422-next.07f7844 linux-x64 node-v12.22.1
- provide a full command that was used to deploy Eclipse Che (including the output)
- provide an output of
chectl version
command
- OperatorHub
- I don’t know
Environment
- my computer
- Windows
- Linux
- macOS
- Cloud
- Amazon
- Azure
- GCE
- CRW Jenkins CI
- Dev Sandbox (workspaces.openshift.com)
- other: please specify
Eclipse Che Logs
Additional context
Related changes: https://github.com/eclipse/che/issues/19460
Issue Analytics
- State:
- Created 2 years ago
- Comments:13 (13 by maintainers)
Top Results From Across the Web
Error Codes | minikube - Kubernetes
minikube failed to create a new Docker Machine api client. “MK_ADDON_DISABLE” (Exit code ExProgramError) minikube could not disable an addon ...
Read more >minikube failed to start - Stack Overflow
You are getting the following error: Exiting due to GUEST_START: Failed kubeconfig update: could not read config: Error decoding config from ...
Read more >Happy path testing may harm your UI - Screenster
In our experience, the happy path is just a starting point. You'd want to start with happy paths testing automation, then expand your...
Read more >Happy path - Wikipedia
Happy path test is a well-defined test case using known input, which executes without exception and produces an expected output. Happy path testing...
Read more >Happy Path Testing With Selenium RC Fu - VMware Tanzu
test /selenium directory. The selenium server must be running before running individual tests. You can start the server with the rake command ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Here are commands to install minikube 1.18.1 which we use in GitHub actions
@tolusha: thank you for the fix! Eclipse Che is now starting successfully on minikube 1.1.1 by using https://github.com/che-incubator/chectl/releases/download/20210423095724/chectl-linux-x64.tar.gz