Rawhide / systemd 250: kernel-install may place kernels and config in the wrong place

Hey folks! So I looked into an interesting bug today where with systemd 250, kernel-install started installing kernels and config snippets to the wrong place. The bug happened on my system because it had, for some reason, these directories: /boot/efi/loader/entries /boot/efi/(machine_id) where (machine_id) is the machine ID from /etc/machine-id. With systemd 250+, if either of those directories exists, kernel- install will write the boot loader config snippets to /boot/efi/loader/entries, but our grub2 config will not find them there. It will *try* to write the kernel files themselves to a subdirectory of /boot/efi/(machine_id); but if that directory doesn't exist, it won't write them anywhere at all. Either way, you won't be able to boot the new kernel. What's supposed to happen is that the config snippets should get written to /boot/loader/entries , and the kernel/initrd files installed to /boot . If you don't have either of the directories listed above, this should still happen and things should work OK. So, my question is...do other Rawhide users have this problem, or is my system an outlier for some reason? I have not been able to figure out *what* created the problematic directories on my system. An earlier systemd rc may have created /boot/efi/(machine_id) if /boot/efi/loader/entries existed, but I don't know what might have created /boot/efi/loader/entries . I'm pretty sure I didn't do it myself, though. I have a patch I can send for systemd to make this behave more like it did previously (before 250, it checked /boot before /boot/efi when deciding which layout was in use; 250 checks /boot/efi before /boot). But it'd be useful to know how many people run into this. It'd also be great if anyone knows how /boot/efi/loader/entries may have come to exist on my system. Thanks folks! -- Adam Williamson Fedora QA IRC: adamw | Twitter: adamw_ha https://www.happyassassin.net