Comment 5 for bug 1926440

The only real bug I see here is that curtin's default partitioning scheme does not create a large enough /boot for this platform. I'll therefore mark this as impacting curtin. IMO, the minimum /boot size for this platform should be able to hold 2 concurrent kernel installs - the current one, and one update. In order to do this, it would need space to hold 4 kernel images and 4 initrds: current and next vmlinuz/initrd.img + uImage/uInitrd and uImage.bak/uInitrd.bak. Also, given that files are first copied into /boot under a temp name then renamed, we also need space to hold the temporary file - the largest of which will be an initrd. Current focal kernels are 11M, and initrds are 82M, and there's about 12M of other content in /boot (System.maps, configs), so we'd need at least:

4 * 11 + 5 + 82 + MAX(11, 82) + 12 = 548M.

@cypressyew: For our testing purposes, I've preseeded a 2G /boot for all of the m400s in our MAAS.