GHA: Put all the preliminary steps into pre-action for s390x

[BbolroC]

This is to introduce a pre-action to all the workflows for building artifacts. The action could take care of tasks such as cleaning up files and reinstalling packages, which prevents a workflow from getting affected by the environment.

This also includes the removal of the step Adjust a permission for repo, because it could be incorporated into the action.

Fixes: #8648

Signed-off-by: Hyounggyu Choi Hyounggyu.Choi@ibm.com

[Amulyam24]

LGTM, Thanks @BbolroC!

[BbolroC]

/test

[stevenhorsman]

Hey @BbolroC - this LGTM. For reference, is the pre_action script, or a summary of the steps that it does available anywhere? I'm thinking that it would be useful to anyone else adding a self-hosted runner to set what things are done in it. I'm not sure the best place to share it though except maybe a list of the steps it does in this commit message?

[BbolroC]

Hey @BbolroC - this LGTM. For reference, is the pre_action script, or a summary of the steps that it does available anywhere? I'm thinking that it would be useful to anyone else adding a self-hosted runner to set what things are done in it. I'm not sure the best place to share it though except maybe a list of the steps it does in this commit message?

They are located in an internal repo for building a self-hosted runner for s390x (ansible-playbook). You can see what is going on in those steps from log for the workflow steps like:

1. Pre-action

Run ${HOME}/script/pre_action.sh ubuntu-2204
Take a pre-action for ubuntu 20.04
Take a pre-action for ubuntu in common
Change the ownership of the workspace
Check if a configuration directory for docker exists
Uninstall k3s if it is installed
Clean up containerd devmapper snapshotter if it is deployed
Re-install docker.io if podman-docker is installed

WARNING: apt does not have a stable CLI interface. Use with caution in scripts.

2. Post-action

Run bash tests/integration/kubernetes/gha-run.sh cleanup-zvsi || true
Gather information about the nodes and pods before cleaning up the node
Creating debugging pod node-debugger-kata-gha-runner-builder-01-xzzpc with container debugger on node kata-gha-runner-builder-01.
Unable to use a TTY - input is not a terminal or the right kind of file
If you don't see a command prompt, try pressing enter.
warning: couldn't attach to pod/node-debugger-kata-gha-runner-builder-01-xzzpc, falling back to streaming logs: 
exec /usr/bin/debug.sh: exec format error
pod "node-debugger-kata-gha-runner-builder-01-xzzpc" deleted
Context "default" modified.
Error from server (NotFound): namespaces "kata-containers-k8s-tests" not found
Take a post-action for ubuntu [22](https://github.com/kata-containers/kata-containers/actions/runs/7194633825/job/19595789928#step:10:23).04
Clean up the files
Clean up the processes
Clean up the mounts
Clean up the crio state
Uninstall k3s
... logs ...
Remove kubectl

If necessary, I could place set -x in the script for better visibility. Thanks!

[stevenhorsman]

You can see what is going on in those steps from log for the workflow steps like

Great point - I didn't think of that. I think that is good enough - thanks!

[BbolroC]

/test