day1 cleanup after the action

[yevgeny-shnaidman]

pull-kernel-module-image.service runs twice: once to pull all the images and reboot the node, and the second time it just checks that everyting has been pulled and exits. During the second time we want to remove the tar of the loaded and saved kernel module image, so that it won't interfere with the correct flow once the node is rebooted again

[netlify]

✅ Deploy Preview for openshift-kmm ready!

Name	Link
🔨 Latest commit	e86dfbc
🔍 Latest deploy log	https://app.netlify.com/sites/openshift-kmm/deploys/65f89784d00dc6000875fc30
😎 Deploy Preview	https://deploy-preview-1055--openshift-kmm.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: yevgeny-shnaidman

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [yevgeny-shnaidman]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[qbarrand]

Don't we want to keep the tarfile so that we don't have to pull it again on next boot?

[yevgeny-shnaidman]

Don't we want to keep the tarfile so that we don't have to pull it again on next boot?

I prefer to use imagePull "Always" policy. Currently the tar file name is always the same, so just to be sure we delete it and pull everything a new. When i get to the issue 898 and issue 920 i will probably change tar file name.
But it is still better to delete it, since it also indicates the presence of the worker image. If for some reason worker image got GCed between reboots, we want to pull it again

[qbarrand]

/lgtm