[odo] odo CLI build issue

[GeekArthur]

Sometimes odo project fails to build due to odo CLI sync issue, the issue is intermittent but it affects both the project build step and adding owner reference step. Temporary workaround is to re-create the OpenShift project, permanent solution is let odo CLI team fix that. Below are detailed logs:

Creating, building and deploying odo application
Step 1 of 4:
- Creating odo component: cw-odonode123
 •  Validating component  ...
 ✓  Validating component [7ms]
Please use `odo push` command to create the component with source deployed
- Successfully created odo component: cw-odonode123
Step 2 of 4:
- Building and deploying odo component: cw-odonode123
Validation
 •  Checking component  ...
 ✓  Checking component [10ms]
Configuration changes
 ✓  Initializing component
 •  Creating component  ...
 ✓  Creating component [188ms]
Pushing to component cw-odonode123 of type local
 •  Checking files for pushing  ...
 ✓  Checking files for pushing [26ms]
 •  Waiting for component to start  ...
 ✓  Waiting for component to start [19s]
 •  Syncing files to the component  ...
E1205 16:22:36.774220   29664 occlient.go:2667] Command 'tar xf - -C /tmp/src --strip 1' in container failed.
E1205 16:22:36.774246   29664 occlient.go:2668] stdout: 
E1205 16:22:36.774255   29664 occlient.go:2669] stderr: tar: /tmp/src: Cannot open: No such file or directory
tar: Error is not recoverable: exiting now
E1205 16:22:36.774268   29664 occlient.go:2670] err: error while streaming command: command terminated with exit code 2
 ✗  Syncing files to the component [240ms]
 ✗  command terminated with exit code 2
- Failed to build and deploy odo component: cw-odonode123

[GeekArthur]

Charlie from odo team said

I believe it may be from pushing too quickly, I've seen this error happen before but only rarely.

[GeekArthur]

I talk with Tomas for this issue and have possible solution, all details are here: https://github.com/openshift/odo/issues/2445