Public bug reported:
The autopkgtest of initramfs-tools fails on armhf on noble:
```
qemu-ata-only SKIP Test lists explicitly supported architectures, but
the current architecture armhf isn't listed.
unit-tests PASS
qemu-klibc FAIL stderr: cryptsetup: ERROR: Couldn't resolve device
/dev/sda2
qemu-busybox FAIL stderr: cryptsetup: ERROR: Couldn't resolve device
/dev/sda2
qemu-virtio-only FAIL stderr: cryptsetup: ERROR: Couldn't resolve device
/dev/sda2
qemu-separate-usr FAIL stderr: cryptsetup: ERROR: Couldn't resolve device
/dev/sda2
qemu-panic-shell FAIL stderr: cryptsetup: ERROR: Couldn't resolve device
/dev/sda2
qemu-net FAIL stderr: cryptsetup: ERROR: Couldn't resolve device
/dev/sda2
qemu-net-dnsmasq FAIL stderr: cryptsetup: ERROR: Couldn't resolve device
/dev/sda2
```
The /usr/sbin/mkinitramfs call in build_initramfs() has following
output:
```
cryptsetup: ERROR: Couldn't resolve device /dev/sda2
cryptsetup: WARNING: Couldn't determine root device
copying from directory
/tmp/autopkgtest.g0n4ix/autopkgtest_tmp/initramfs-test.qV8LgntBoK/rootdir
```
The two cryptsetup log lines are printed by /usr/share/initramfs-
tools/hooks/cryptroot (which comes from cryptsetup-initramfs)
** Affects: cryptsetup (Ubuntu)
Importance: Undecided
Status: New
** Affects: initramfs-tools (Ubuntu)
Importance: Undecided
Status: New
** Tags: update-excuse
** Also affects: initramfs-tools (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/2043579
Title:
initramfs-tools autopkgtest fails on armhf: stderr: cryptsetup: ERROR:
Couldn't resolve device /dev/sda2
Status in cryptsetup package in Ubuntu:
New
Status in initramfs-tools package in Ubuntu:
New
Bug description:
The autopkgtest of initramfs-tools fails on armhf on noble:
```
qemu-ata-only SKIP Test lists explicitly supported architectures, but
the current architecture armhf isn't listed.
unit-tests PASS
qemu-klibc FAIL stderr: cryptsetup: ERROR: Couldn't resolve device
/dev/sda2
qemu-busybox FAIL stderr: cryptsetup: ERROR: Couldn't resolve device
/dev/sda2
qemu-virtio-only FAIL stderr: cryptsetup: ERROR: Couldn't resolve device
/dev/sda2
qemu-separate-usr FAIL stderr: cryptsetup: ERROR: Couldn't resolve device
/dev/sda2
qemu-panic-shell FAIL stderr: cryptsetup: ERROR: Couldn't resolve device
/dev/sda2
qemu-net FAIL stderr: cryptsetup: ERROR: Couldn't resolve device
/dev/sda2
qemu-net-dnsmasq FAIL stderr: cryptsetup: ERROR: Couldn't resolve device
/dev/sda2
```
The /usr/sbin/mkinitramfs call in build_initramfs() has following
output:
```
cryptsetup: ERROR: Couldn't resolve device /dev/sda2
cryptsetup: WARNING: Couldn't determine root device
copying from directory
/tmp/autopkgtest.g0n4ix/autopkgtest_tmp/initramfs-test.qV8LgntBoK/rootdir
```
The two cryptsetup log lines are printed by /usr/share/initramfs-
tools/hooks/cryptroot (which comes from cryptsetup-initramfs)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cryptsetup/+bug/2043579/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
