initramfs-tools autopkgtest fails on armhf: stderr: cryptsetup: ERROR: Couldn't resolve device /dev/sda2

Bug #2043579 reported by Benjamin Drung
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Auto Package Testing
New
Undecided
Unassigned
cryptsetup (Ubuntu)
Invalid
Undecided
Unassigned
initramfs-tools (Ubuntu)
Fix Released
Undecided
Unassigned

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)

Revision history for this message
Benjamin Drung (bdrung) wrote :

On 2023-12-06 the warning vanished.

Changed in initramfs-tools (Ubuntu):
status: New → Invalid
Changed in cryptsetup (Ubuntu):
status: New → Invalid
Revision history for this message
dann frazier (dannf) wrote :
Changed in cryptsetup (Ubuntu):
status: Invalid → New
Changed in initramfs-tools (Ubuntu):
status: Invalid → New
Revision history for this message
dann frazier (dannf) wrote :

Comparing the artifacts between a failed and successful log, the relevant difference appears to be that cryptsetup-initramfs is only installed in the failed log. These errors also appear during the setup phase when package installation causes the initramfs for the host to be updated:

3870s Processing triggers for initramfs-tools (0.142ubuntu15.1) ...
3870s Processing triggers for linux-image-6.5.0-15-generic (6.5.0-15.15) ...
3870s /etc/kernel/postinst.d/initramfs-tools:
3870s update-initramfs: Generating /boot/initrd.img-6.5.0-15-generic
3874s cryptsetup: ERROR: Couldn't resolve device /dev/sda2
3874s cryptsetup: WARNING: Couldn't determine root device

So this seems like a host configuration issue. Is there a LP project for those for which we could add a task?

dann frazier (dannf)
Changed in initramfs-tools (Ubuntu):
status: New → Triaged
Changed in cryptsetup (Ubuntu):
status: New → Invalid
dann frazier (dannf)
no longer affects: cryptsetup (Ubuntu Mantic)
no longer affects: cryptsetup (Ubuntu Noble)
no longer affects: initramfs-tools (Ubuntu Mantic)
no longer affects: initramfs-tools (Ubuntu Noble)
Revision history for this message
Benjamin Drung (bdrung) wrote :

The autopkgtest of initramfs-tools on armhf on noble started to succeed again (roughly on 2023-12-26).

Changed in initramfs-tools (Ubuntu):
status: Triaged → Fix Released
Revision history for this message
dann frazier (dannf) wrote :

Yeah - maybe its just the mantic builder image that has the bad cryptsetup config (/etc/crypttab)?

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.