Comment # 18 on bug 1226122 from Josef Reidinger

(In reply to Lukas Ocilka from comment #10)
> Josef, can you please take a look at this? Does it work as designed? I don't
> see any change in yast2-bootloader that would be relevant. If anything then
> only those changes for systemd-boot. Is this even anything for us?

Well, Yast as installer does not copy anything anywhere. It just calls other
binaries and writes configs. For no bootloader no config is written beside
/etc/sysconfig/bootloader. And also we do not call anything as possible use
case for none bootloader can be also to load kernel from network and having
just minimal system.

Mario: what you can try to make it work is:
1. call on installed system `dracut --all --regenerate-all` if it generates
files for you.
2. if you can boot installation env as legacy, it can possibly fill /boot as it
is common location on legacy. You boot it as EFI, which writes stuff into ESP
partition ( and nowhere in your case as no bootloader script is called )