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?

-- 
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:
  Invalid
Status in initramfs-tools package in Ubuntu:
  Triaged

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

Reply via email to