[prod-preview] Problems starting Che 6 workspaces

[Katka92]

Issue Overview

Tests running against prod-preview cluster 2a are sometimes failing on "Unable to provision" error.
In a log, I can see:

"Starting workspace 'osio-ci-preview-rhche-periodical/workspace1ipeen' with id 'workspacegsxr6kkf28clx0ze' by user 'osio-ci-preview-rhche-periodical'"
"Failed to start Kubernetes runtime of workspace workspacegsxr6kkf28clx0ze. Cause: Bootstrapping of machine dev-machine failed. Cause: error dialing backend: dial tcp 172.31.74.108:10250: connect: cannot assign requested address"
"Workspace 'osio-ci-preview-rhche-periodical:workspace1ipeen' with id 'workspacegsxr6kkf28clx0ze' start failed"
"Could not get runtimeIdentity for workspace 'workspacegsxr6kkf28clx0ze', and so cannot verify if current subject '34a25092-f30d-4478-a8f5-771b077e517d' owns workspace" - more similar messages appears, just with another "current subject"

Steps To Reproduce

I wasn't able to preproduce it manually today.

Additional Information

Job with failures: https://ci.centos.org/job/devtools-rh-che-periodic-prod-preview-2a/204/console
Username: osio-ci-preview-rhche-periodical
Environment: che.prod-preview.openshift.io
Cluster: 2a

[gorkem]

Is this a multi-container workspace?

[Katka92]

I was starting vert-x workspace with project vertx-http-booster. So as far as I understand, it is not multi-container workspace.

[Katka92]

Today I'm able to reproduce it manually via Dashboard with user osio-ci-preview-rhche-periodical and user kkanova-preview. I'm getting this error in UI [1]. Both accounts are provision against use-east-2a cluster on prod-preview.

[1]

[ibuziuk]

@Katka92 is it prod-preview specific ?

[Katka92]

@ibuziuk speaking about periodic jobs, this error was seen only on prod-preview. Today I've tried it manually again and I was not able to reproduce it.

[ibuziuk]

closing since rh-che specific issue is also closed redhat-developer/rh-che#1282 There is a problem with slow gluster / long cloning, but @rhopp already created a separate issue for this redhat-developer/rh-che#1289