devworkspace fails to start when init container exited but the error is not helpful for end-users

[benoitf]

Starting a devWorkspace, I've the error

NAMESPACE         NAME               DEVWORKSPACE ID             PHASE    INFO
opentlc-mgr-che   spring-petclinic   workspacec4b044cd3dfa4a26   Failed   Init Container project-clone has state CrashLoopBackOff

It would be nice to have a better error reporting for end-users

The root cause, after grabbing logs is:

2021/06/03 13:57:09 Read DevWorkspace at /devworkspace-metadata/flattened.devworkspace.yaml
2021/06/03 13:57:09 Cloning project spring-petclinic to spring-petclinic
2021/06/03 13:57:09 failed to clone project spring-petclinic: project checkoutFrom refers to non-existing remote

so it could be nice to have the error reported directly instead of seeing that a container is in CrashLoopBack state

[sleshchenko]

Well, I would distinct three issues:

• Probably we should do it with validating webhooks; Implement validation webhooks which would validate devfile consistency #479
• Errors during project clone are not reported #457
• DWO should somehow report crashed container logs to user DWO should somehow report crashed container logs to user #579;

[sleshchenko]

Closing this issue since two improvements are done and you won't face the same behavior.