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.
Bug 1861858 - grub2 should get resynced with 7.8 branch
Summary: grub2 should get resynced with 7.8 branch
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: grub2
Version: 7.4
Hardware: Unspecified
OS: Unspecified
Target Milestone: rc
: ---
Assignee: Bootloader engineering team
QA Contact: Release Test Team
Depends On: 1861860 1861861
Blocks: 1861857
TreeView+ depends on / blocked
Reported: 2020-07-29 18:04 UTC by Ray Strode [halfline]
Modified: 2022-07-09 11:39 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1861855
Last Closed: 2020-08-03 11:14:37 UTC
Target Upstream Version:

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2020:3275 0 None None None 2020-08-03 11:14:42 UTC

Description Ray Strode [halfline] 2020-07-29 18:04:05 UTC
As part of the fixes for CVE-2020-10713 grub needs to be resynced with the 7.8 branch.

This bug is to track that resync.

Comment 2 Ray Strode [halfline] 2020-07-29 18:11:18 UTC
The resync brings in these fixes:

bug 1340893: grubby --default-title doesn't print anything
bug 1402716: grub2-install failed in rear recover with /boot partition formatted with XFS
bug 1446418: grub2 efidisk identifying cd/dvd drive as hd
bug 1457988: Grub2 pagefaults with nvidia GPU on some HPE UV/Hawks2 systems
bug 1483740: pxe booting with grubaa64.efi adds extra "-" to config filename
bug 1496952: grub2-efi-x64 and shim-x64 packages will always fail rpm --verify if /boot/efi is mounted
bug 1497918: /boot/grub2/grubenv is changed into a dead symlink by installing grub2-efi package on non-uefi machine
bug 1512749: grub2-setpassword ignores -o (--output_path) command line option
bug 1594703: grub2-install: error: /usr/lib/i386-pc/i386-pc/modinfo.sh doesn't exist. Please specify --target or --directory.
bug 1602773: grub2-editenv: error: cannot rename the file /boot/grub2/grubenv.new to /boot/grub2/grubenv: No such file or directory.
bug 1614259: grub2 should depend on  /usr/lib/libc.so instead of glibc32, causes rpmbuild --rebuild to fail
bug 1616395: grub2 doesn't handle relative paths correctly for UEFI HTTP Boot
bug 1732765: UEFI HTTP boot over IPv6 does not work
bug 1748019: Broken upgrade for non-intel arches beause of wrong efi provides

Comment 9 errata-xmlrpc 2020-08-03 11:14:37 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.


Note You need to log in before you can comment on or make changes to this bug.