Comment 1 for bug 2011925

I had a nasty feeling this might rear its head on some platform. The question in this case is: why is the kernel stuck in half-configured state?

The new flash-kernel test is expecting that to resolve to "installed" before it can proceed because otherwise it risks flashing the kernel, but failing to flash the initrd (or flashing an invalid initrd).

In fact, that looks like the correct decision here because I don't see the initramfs-tools trigger firing to generate the initrd? The line at the top ("I: /boot/initrd.img is now a symlink to initrd.img-6.1.0-16-generic") doesn't mean the initrd exists, just that the symlink has been created and at this stage, at least on Xilinx and Pi images, that means the symlink is dead and definitely should not be flashed; once the kernel package is fully "installed", we can be certain the initrd exists and is correct.