Enabling a new adhoc gitlab-runner
One or more of the native gitlab-runners is down, and pipelines get stuck in
build-tools stages because no native GitLab runners of a certain
architecture are available.
Escalate the unavailable runners via all appropriate channels. Make sure it is understood that this breaks all kernel development and delivery, especially for CVE fixes.
Checkout and cd to
deployment-all, export the encryption password:
Setup one or more new adhoc Beaker machines for the required architecture via
podman run \ --network host \ --env ENVPASSWORD \ --interactive \ --rm \ --tty \ --volume .:/data:z \ --workdir /data \ quay.io/cki/cki-tools:production \ ./beaker_provision.sh adhoc-N-ARCH
Replace N by a running number (1, 2) and ARCH by the required architecture (
Wait until the machines are provisioned. The machines should be automatically added to
ansible/inventory/beaker.yml. Create a new merge request with this change.
On the MR pipeline, switch to the jobs page. In order, execute the following jobs:
scripts: [gitlab-runner-config, configurations apply]
When playbooks have completed successfully for the new hosts (jobs will fail for offline hosts), you can proceed to merge the change.
When the adhoc gitlab-runners are not needed anymore, run the following to return the machines and remove them from
podman run \ --network host \ --env ENVPASSWORD \ --interactive \ --rm \ --tty \ --volume .:/data:z \ --workdir /data \ quay.io/cki/cki-tools:production \ ./beaker_cancel.sh adhoc-N-ARCH
As above, create and merge a merge request with this change.