Open Stack

Has anyone else tried building Debian Testing (bookworm) images with DIB?
I'm having troubles with getting them to boot, with errors that look like
missing components in the initrd to me. The command I am using to build is:

export ELEMENTS_PATH=elements:diskimage-builder/diskimage_builder/elements
export DIB_CLOUD_INIT_DATASOURCES="ConfigDrive, OpenStack, NoCloud"
export DIB_APT_MINIMAL_CREATE_INTERFACES=0
export DIB_PYTHON_VERSION=3
export DIB_RELEASE=bookworm
export DIB_SF_AGENT_PACKAGE=shakenfist-agent
export build_args="cloud-init cloud-init-datasources sf-agent vm"

disk-image-create utilities debian debian-systemd ${build_args} -o
temp.qcow2

Where shakenfist-agent / sf-agent are a custom element not really relevant
to this query (I've left it for completeness).

When I boot the output image, I get this:

...
[    1.906949] virtio_blk virtio2: 2/0/0 default/read/poll queues
[    1.908318] virtio_blk virtio2: [vda] 104857600 512-byte logical blocks
(53.7 GB/50.0 GiB)
[    1.916912]  vda: vda1
[    1.917646] virtio_blk virtio3: 2/0/0 default/read/poll queues
[    1.917676] virtio_net virtio1 ens11: renamed from eth0
[    1.918965] virtio_blk virtio3: [vdb] 184 512-byte logical blocks (94.2
kB/92.0 KiB)
Begin: Loading essential drivers ... done.
Begin: Running /scripts/init-premount ... done.
Begin: Mounting root file system ... Begin: Running /scripts/local-top ...
done.
Begin: Running /scripts/local-premount ... done.
Warning: fsck not present, so skipping root file system
[    2.024351] EXT4-fs (vda1): mounted filesystem with ordered data mode.
Quota mode: none.
done.
Begin: Running /scripts/local-bottom ... [    2.041352] EXT4-fs (vda1):
unmounting filesystem.
GROWROOT: WARNING: resize failed: failed [flock:127] flock -x 9
/sbin/growpart: line 714: flock: not found
FAILED: Error while obtaining exclusive lock on /dev/vda
[    2.057556]  vda: vda1
/scripts/local-bottom/growroot: line 97: wait-for-root: not found
done.
Begin: Running /scripts/init-bottom ... mount: mounting /dev on /root/dev
failed: No such file or directory
mount: mounting /dev on /root/dev failed: No such file or directory
done.
mount: mounting /run on /root/run failed: No such file or directory
BusyBox v1.35.0 (Debian 1:1.35.0-4+b1) multi-call binary.

Usage: run-init [-d CAP,CAP...] [-n] [-c CONSOLE_DEV] NEW_ROOT NEW_INIT
[ARGS]

Free initramfs and switch to another root fs:
chroot to NEW_ROOT, delete all in /, move NEW_ROOT to /,
execute NEW_INIT. PID must be 1. NEW_ROOT must be a mountpoint.

-c DEV Reopen stdio to DEV after switch
-d CAPS Drop capabilities
-n Dry run
Target filesystem doesn't have requested /sbin/init.
BusyBox v1.35.0 (Debian 1:1.35.0-4+b1) multi-call binary.

Usage: run-init [-d CAP,CAP...] [-n] [-c CONSOLE_DEV] NEW_ROOT NEW_INIT
[ARGS]

Free initramfs and switch to another root fs:
chroot to NEW_ROOT, delete all in /, move NEW_ROOT to /,
execute NEW_INIT. PID must be 1. NEW_ROOT must be a mountpoint.
...

Which looks to me like I am missing fsck, flock and wait-for-root, probably
in the initrd? Adding cloud-init-growpart and growroot as elements did not
help, neither did ensuring that the image contained cloud-guest-utils or
util-linux.

I wonder if anyone else has seen this and has some hints?

Thanks,
Michael
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.openstack.org/pipermail/openstack-discuss/attachments/20230118/2496ee13/attachment-0001.htm>