When installing on ppc64(le) with recent Rawhide and Fedora 27 composes, bootloader install always fails. program.log shows:
08:52:12,037 INF program: Running... grub2-install --no-nvram --no-floppy /dev/vda1
08:52:12,386 INF program: Installing for powerpc-ieee1275 platform.
08:52:12,387 INF program: grub2-install: error: not a HFS+ filesystem.
08:52:12,388 DBG program: Return code: 1
Note, /dev/vda1 is a PPC PReP boot partition (per storage.log).
It looks like this broke between grub2-2.02-7 and grub2-2.02-10; it's very likely it broke in grub2-2.02-8, which bumped to a newer 'upstream' (i.e. a bunch of new patch files).
The program.log from a successful install on a compose that included the -7 package looks like this:
20:31:04,505 INF program: Running... grub2-install --no-nvram --no-floppy /dev/vda1
20:31:04,838 INF program: Installing for powerpc-ieee1275 platform.
20:31:04,840 INF program: Installation finished. No error reported.
so the detected platform hasn't changed, but -7 was happy installing to a PReP boot partition, while -10 (probably -8) is not. Perhaps some upstream change erroneously assumes all powerpcs are also Macs?
Created attachment 1317168 [details]
program.log from an install that hit the bug (with grub2 -10)
Created attachment 1317169 [details]
storage.log from an install that hit the bug (with grub2 -10)
Created attachment 1317170 [details]
program.log from an install that did NOT hit the bug (with grub2 -7)
Created attachment 1317171 [details]
storage.log from an install that did NOT hit the bug (with grub2 -7)
Unable to validate the proposed correction because
with last composes Rawhide and F27 20170827 most probably packaging error because iso boot failed as per https://openqa.stg.fedoraproject.org/tests/150260#step/_do_install_and_reboot/18
Yeah, there was another round of grub2 / shim package naming issues. We *hope* the next compose that actually manages to complete (there was also another round of weirdness on the compose hosts...) will have all the issues solved at last.
correction of this bug validated on openQA with Rawhide compose 20170830
This bug appears to have been reported against 'rawhide' during the Fedora 28 development cycle.
Changing version to '28'.
This message is a reminder that Fedora 28 is nearing its end of life.
On 2019-May-28 Fedora will stop maintaining and issuing updates for
Fedora 28. It is Fedora's policy to close all bug reports from releases
that are no longer maintained. At that time this bug will be closed as
EOL if it remains open with a Fedora 'version' of '28'.
Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version.
Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 28 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.
Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.
Per #c7, this was fixed.