che: Factory sometimes doesn't create workspace
Describe the bug
From time to time, a workspace that should be created and started via factory URL is not even created. The UI is stuck on the first step and no error is shown to the user. This problem was reproduced manually and was also caught by nightly tests against nightly Che build.
Che version
- latest
- nightly
- other: please specify
Steps to reproduce
- Login to che
- Past factory link to the URL:
<che_url>/f?url=https://raw.githubusercontent.com/eclipse/che-devfile-registry/master/devfiles/java-maven/devfile.yaml - Wait for factory page to be loaded.
Expected behavior
The workspace should be created and started or some error should be shown to the user.
Runtime
- kubernetes (include output of
kubectl version) - Openshift (include output of
oc version) - minikube (include output of
minikube versionandkubectl version) minikube v1.1.1 on linux (amd64) - minishift (include output of
minishift versionandoc version) - docker-desktop + K8S (include output of
docker versionandkubectl version) - other: (please specify)
Screenshots

Installation method
- chectl chectl/0.0.20200721-next.cf7baad linux-x64 node-v10.21.0
chectl server:start --k8spodreadytimeout=180000 --listr-renderer=verbose --platform=minikube --che-operator-cr-patch-yaml=/mnt/hudson_workspace/workspace/basic-MultiUser-Che-check-e2e-tests-against-k8s/custom-resource-patch.yaml
- provide a full command that was used to deploy Eclipse Che (including the output)
- provide an output of
chectl versioncommand
- OperatorHub
- I don’t know
Environment
- my computer
- Windows
- Linux
- macOS
- Cloud
- Amazon
- Azure
- GCE
- other (please specify)
- other: please specify
Eclipse Che Logs
About this issue
- Original URL
- State: closed
- Created 4 years ago
- Comments: 16 (16 by maintainers)
@sleshchenko I reproduced that on nightly, on che.openshift.io there is 7.16.0 (should be updated to 7.16.2 early next week) so I’m not sure if that can be a difference. I’ll try to reproduce that manually and if I’ll be successful, I’ll share the requests history.