[17:49] <Odd_Bloke> o/ We've noticed that the initrd in cloud images doesn't include the fsck binary.  This is causing problems for our users when they need to do root disk recovery for some reason.  https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1917780 ensured it would always be present when update-initramfs runs (and, indeed, that's the workaround we're currently considering), which suggests
[17:49] -ubottu:#ubuntu-server- Launchpad bug 1917780 in initramfs-tools (Ubuntu Groovy) "initramfs-tools does not include fsck binaries in the initrd if all mount pass are 0" [Critical, Fix Released]
[17:49] <Odd_Bloke> to me this is a bug in the cloud image build.  Does anyone know if this is intentional?  (Shall I file a cloud-images bug?) 
[17:59] <Odd_Bloke> Interestingly it _is_ included in jammy-server-cloudimg-amd64-disk-kvm.img's initrd, but not in jammy-server-cloudimg-amd64.img's.
[18:09] <Odd_Bloke> philroche: You're the right person to bug about ^, I think?
[18:11] <MTecknology> lol ... I've been putting off digging into a different initramfs bug on ubuntu.
[18:12] <MTecknology> (in favor of easier bugs, but I gotta deal with it this week)
[20:46] <sarnold> heya Odd_Bloke; that does feel like it's worth a bug, even if it's intentional, just to have a nice solid place for others to find :)