OpenShift SNO installation fails due to disk issue

4.12.9

Always

1. I'm using VirtualBox VMs for my activities
2. Such is my openshift-install:
$ ./openshift-install version
./openshift-install 4.12.9
built from commit 15d8ffe8fa3a5ab2f36f7e0a54126c98733aaf25
release image quay.io/openshift-release-dev/ocp-release@sha256:96bf74ce789ccb22391deea98e0c5050c41b67cc17defbb38089d32226dba0b8
release architecture amd64
3. Following this guide:
https://docs.openshift.com/container-platform/4.12/installing/installing_sno/install-sno-installing-sno.html

in my install-config.yaml I've specified such:
bootstrapInPlace:
  installationDisk: /dev/sda

and at one point I was trying this as well:
bootstrapInPlace:
  installationDisk: /dev/disk/by-uuid/098efc7e-61c7-453c-9447-08c1fc87169e

4. Later when booting node and invoking:
journalctl -b -f -u release-image.service -u bootkube.service

I could see such as part of output:
Mar 24 11:00:47 localhost.localdomain mco-render[3417]: I0324 11:00:47.812192       1 bootstrap.go:115] Version: v4.12.0-202303211829.p0.gf6c2197.assembly.stream-dirty (f6c21976e39cf6cb9e2ca71141478d5e612fb53f)
Mar 24 11:00:47 localhost.localdomain bootkube.sh[3379]: I0324 11:00:47.812192       1 bootstrap.go:115] Version: v4.12.0-202303211829.p0.gf6c2197.assembly.stream-dirty (f6c21976e39cf6cb9e2ca71141478d5e612fb53f)
...
Mar 24 11:00:54 localhost.localdomain bootkube.sh[3530]: Error: writing blob: adding layer with blob "sha256:574a629d49fb802ef3c0c44136c7a2fcae2433f35e8726aafa382b93126421f1": processing tar file(write /usr/bin/cloud-credential-operator: no space left on device): exit status 1
Mar 24 11:00:54 localhost.localdomain podman[3530]: 2023-03-24 11:00:48.423004355 +0000 UTC m=+0.038298608 image pull  quay.io/openshift-release-dev/ocp-v4.0-art-dev@sha256:8b00b19eaa20b00e263a9f344fc6e3ea4700c38d4c25638bc585d4b41ae0d9fd
Mar 24 11:00:54 localhost.localdomain systemd[1]: bootkube.service: Main process exited, code=exited, status=125/n/a
Mar 24 11:00:54 localhost.localdomain systemd[1]: bootkube.service: Failed with result 'exit-code'.
Mar 24 11:00:54 localhost.localdomain systemd[1]: bootkube.service: Consumed 32.905s CPU time.
Mar 24 11:00:59 localhost.localdomain systemd[1]: bootkube.service: Scheduled restart job, restart counter is at 1.
Mar 24 11:00:59 localhost.localdomain systemd[1]: Stopped Bootstrap a Kubernetes cluster.

5. When doing SSH to check my disks - I have such (see presence of sda as ext4 there):

[core@localhost ~]$ lsblk -f
NAME  FSTYPE FSVER       LABEL                       UUID                                 FSAVAIL FSUSE% MOUNTPOINTS
loop0 xfs                                            fec9dd9c-07cb-47a7-8972-01cf24f09dd0   76.5M    95% /var/lib/containers/storage/overlay
                                                                                                         /var
                                                                                                         /etc
                                                                                                         /run/ephemeral
loop1 squash 4.0                                                                                0   100% /usr
                                                                                                         /boot
                                                                                                         /
                                                                                                         /sysroot
sda   ext4   1.0                                     098efc7e-61c7-453c-9447-08c1fc87169e                
sr0   iso966 Joliet Exte rhcos-413.92.202303011445-0 2023-03-01-15-28-55-00                     0   100% /run/media/iso

Failing bootkube sequence

Working bootkube sequence and with some log line about mount of installationDisk