Description of problem:

This issue describes the root issue for https://issues.redhat.com/browse/CRW-8363.

When a workspace is started this error occurs:

Error creating DevWorkspace deployment: Detected unrecoverable event FailedScheduling: 0/18 nodes are available: pod has unbound immediate PersistentVolumeClaims. preemption: 0/18 nodes are available: 18 Preemption is not helpful for scheduling...'

Even though the event is FailedScheduling which is specified by default as an ignoredUnrecoverableEvents, it is not being ignored and workspace fails to start with the above error.

The DevWorkspace Operator is erroneously not ignoring the FailedScheduling event and returning an error here: https://github.com/devfile/devworkspace-operator/blob/799c0c493a44f867f168efd951da768d9094bec8/controllers/workspace/devworkspace_controller.go#L489-L495. A possible solution might be to have the DevWorkspace operator retry the reconcile.

Workaround:
For the specific error above, using a storage class with

volumeBindingMode: WaitForFirstConsumer

And setting the storage class in the CheCluster under{{spec.devEnvironments.storage}} should prevent the error.