Cannot start workspace with Openshift storage class mode with WaitForFirstConsumer value

Describe the bug

When default StorageClass is configured to have volumeBindingMode set to WaitForFirstConsumer, workspaces do not start.

Che version

• latest
• nightly
• other: please specify

Steps to reproduce

1. Consume a factory by “https://[your path to Che]f?url=https://raw.githubusercontent.com/redhat-developer-demos/guru-night/master/quarkus-tutorial/devfile.yaml url”.

Expected behavior

The factory consumed properly with creation a workspace.

Runtime

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

Screenshots

Installation method

• chectl
• che-operator
• minishift-addon
• I don’t know

Environment

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

Additional context

Codeready issue - https://issues.jboss.org/browse/CRW-294.

[dmytro-ndp]

“WaitForFirstConsumer” is default setting of OpenShift 4.x on AWS. Looks like it’s usual mode for instances on AWS, Azure, … So we need to support it.

[sleshchenko]

Just to extend context a bit: previously it used to work, but after some upgrading of OpenShift version, OS starts to propagate events with FailedScheduling if WaitForFirstConsumer is used. The second workspace start - works just fine and If Che would wait a couple of seconds - PVC would be mounted successfully. So, the easiest solution here is to remove FailedScheduling from the default unrecoverable events list. It was initially added for some issue on OSIO, so if we just remove it - some workspaces may exceed workspace timeout instead of early failure. Maybe OSIO case should be investigated more and event message should be concreted instead of catching all FailedScheduling, like FailedScheduling: no available node is found(<-just an example)

cc @ibuziuk