Unexpected errors during workspace creation based on Pet clinic project

[musienko-maxim]

Description

• During creation and running the workspace from devfile (the file create workspace based on Pet clinic application) on CI we have the errors like this:

1. Unknown error happened, try to reload page

• logs_with_screenshot.zip
• logs_with_screenshot_2.zip

2. Failed to start Kubernetes runtime of workspace <ws_name>. Cause: Waiting for Kubernetes environment 'default' of the <ws_name> reached timeout
   logs_with_screenshot_3

• All errors look pretty similar. They have problems with communication through WebSocket channel. It influence on stability of the HappyPath scenario

Reproduction Steps

It reproduces on the job: https://codeready-workspaces-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/CHE-7-Happy-Path-Tests/, which is launched every hour.

• At first step we run minikube with next command: minikube start --vm-driver=kvm2 --cpus 2 --memory 10240 --docker-opt userland-proxy=false
• The che is deployed with chectlin next way: ./chectl server:start --k8spodreadytimeout=180000
• After, we create a workspace with devfile: ./chectl workspace:start --devfile=k8s-devfile.yaml
  k8s-devfile.zip
  OS and version:
  The Jenkins env. based on 8RHEL 7 VM (32GM memory RAM, 16CPU, 40GB DISK) , with Minikube + KVM, latest chectl version.

[metlos]

In the provided server log, you can find Message: etcdserver: request timed out. so this seems to be an issue with kubernetes itself where the requests that che sends to it are timing out.

[skabashnyuk]

devfile is working on my minishift. Probably some issue with Minikube + KVM environment. @musienko-maxim can you try the same devfile on different OpenShift flavors?

[musienko-maxim]

I am going to try and report.

[l0rd]

@musienko-maxim should we close this issue?

[musienko-maxim]

not actual