RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

If my TFTP server is x86_64 but I want to boot ppc64 systems from it, I have to find a ppc64 system and run grub2-mknetdir on it to produce the necessary files and then copy them over to my TFTP server. Or else I have to do rpm --force to install the ppc64 package on the wrong arch and hope I don't screw up my system's GRUB2 in the process.

It would be nice if GRUB2 could produce the necessary files for any arch on any other arch.

One possible way might be to use the trick with noarch subpackage with conditional %files, as used by ipxe-bootimgs for example. Each arch would have its own separate noarch subpackage containing the relevant images, for example grub2-bootimgs-i386-pc would have /usr/lib/grub/i386-pc built on x86, grub2-bootimgs-powerpc-ieee1275 would have /usr/lib/grub/powerpc-ieee1275 built on ppc64, etc. Then I could install grub2-bootimgs-powerpc-ieee1275 on my x86 TFTP server and use grub2-mknetdir -d /usr/lib/grub/powerpc-ieee1275 to get the images for booting ppc64 machines.

After evaluating this issue, there are no plans to address it further or fix it in an upcoming release.  Therefore, it is being closed.  If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened.