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.

Description of problem:

recent update of grub2 removes grub2 package and replaces it with relevant arch specific rpms (grub2-pc, grub2-ppc64le ...) which affects a log of things.

This bug is here so other components can refer to it

example of affected issues: 

anaconda
rcm kickstarts used for qcow creation
rcm comps

This is a issue to track such change so other bugs can reference it. I wasn't able to find such bug in https://errata.devel.redhat.com/advisory/27621

The relevant grub2 package should be added automatically to the installation transaction if Anaconda is doing the bootloader installation.

But I can see at least two other use cases being affected:

- people doing custom bootloader installation via a %post script (due to some exotic setup that Anaconda does not support, etc.) - they would have the grub2 package listed in the %packages section and their kickstarts will start to fail due missing package (grub2)

- people who think they have to list grub2 in packages section even when this is actually not needed (eq. Anaconda does bootloader installation & adds the packages to transaction) - their kickstarts will also stop working due to a missing package

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.