Comment # 38 on bug 1226122 from Felix Miata

(In reply to Martin Wilck from comment #35)
> (In reply to Felix Miata from comment #32)

> > That one bootloader works because some bootloader is able to find boot files
> > in an expected location on some filesystem for each installed system in the
> > machine, most logically in a location identified as boot! 

> Sorry, I am not getting this. Do you mean systemd-boot with "that one boot
> loader"? Did you select systemd-boot or not? And if yes, why? AFAICT
> systemd-boot abandons /boot, which is exactly what you rant about in the
> rest of your comment.

That one bootloader on my legacy booters is openSUSE's grub 0.9x (usually
pre-Leap) using gfxboot with penguin=100, not grub2. On UEFI systems it is TW's
grub2-x86-64-efi.

I selected neither grub nor systemd-boot. I selected bootloader not manged, and
efibootmgr, not knowing I also needed to make some additional selection
necessary to be able to find kernel & initrd in a tradtional location. IIRC, I
made no selection of anything else that I knew had anything to do with booting
except for efibootmgr. Maybe if it needs to be known, all I selected can be
determined from attachment  875394 [details].

(In reply to Alberto Planas Dominguez from comment #37)

> if no bootloader is installed, seems that sdbootutil-rpm-scriptlets is
> preferred by the solver.

Again, installing neither grub components nor BLS-spec components does not
equate to absence of files in some co-location necessary /to/ boot. As long as
the error reported here remains substantially likely for any multibooter (or
anyone who pre-partitions to his desires 100% supported, BTW), the boot
selection portion of the installer's job is incomplete. "Not Managed" can no
longer be allowed to equate no /bootloader/ is installed, regardless of intent
to transition default to BLS location. It's not managed alright - it's random.
The "Boot Loader Settings" page boils down to does a bootloader need to be
installed, and if so which, not do we need linux and initrd installed somewhere
when kernels are installed. The "Boot Loader" select list, or elsewhere in the
"Boot Code Options", or radio buttons, or select list, or a novel tab, needs
inclusion to somehow take into account where these two files need to go when
neither GRUB2 nor GRUB2 for EFI nor Systemd Boot are selected, unless under the
covers the scripts, "distro level", as Lukas wrote, can reliably determine the
right choice reliably.