while setting up provisioner, check if osie file path is valid

[Cbkhare]

Description

While creating provisioner, if TB_OSIE_TAR is set then osie file is extracted from the file whose location/absolute path is the value of this variable.

Why is this needed

if TB_OSIE_TAR is set and the file is not present at the given path(value of TB_OSIE_TAR) workflow fails stating the Linux image is not found. Which is valid as osie directory under deploy/state would be empty.

• check has been added to verify if the file is present in the given path or not.

How Has This Been Tested?

By creating the provisioner.
Provisioner is not created if a tar file is present at the location defined in TB_OSIE_TAR.

on success

On failure

[codecov]

Codecov Report

Merging #411 (c286026) into master (8ea8a0e) will not change coverage.
The diff coverage is n/a.

❗ Current head c286026 differs from pull request most recent head 1bf3b3d. Consider uploading reports for the commit 1bf3b3d to get more accurate results

@@           Coverage Diff           @@
##           master     #411   +/-   ##
=======================================
  Coverage   32.70%   32.70%           
=======================================
  Files          44       44           
  Lines        3137     3137           
=======================================
  Hits         1026     1026           
  Misses       2019     2019           
  Partials       92       92           

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 8ea8a0e...1bf3b3d. Read the comment docs.

[mmlb]

Shouldn't this already be caught by tar exiting with an error and set-e being set?

[Cbkhare]

Shouldn't this already be caught by tar exiting with an error and set-e being set?

@mmlb , right, I think the script is not bailing out in that case. With this PR it goes for a graceful exit.

[tstromberg]

This PR looks great! The DCO checker noticed that one of your git commits isn't signed properly - can you fix that so that this PR may be merged?

https://github.com/tinkerbell/tink/pull/411/checks?check_run_id=2999422937 has instructions on how to fix this PR.

[gauravgahlot]

@tstromberg I tried those steps already but didn't work. Will it be okay if I close this PR and create a new one?
I know the original contributor personally and I don't think he is looking into Tinkerbell anymore.

[nshalman]

@tstromberg I tried those steps already but didn't work. Will it be okay if I close this PR and create a new one?
I know the original contributor personally and I don't think he is looking into Tinkerbell anymore.

@gauravgahlot That would be great. I'll close out this one.