Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

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 1402716

Summary:	grub2-install failed in rear recover with /boot partition formatted with XFS
Product:	Red Hat Enterprise Linux 7	Reporter:	Masahiro Matsuya <mmatsuya>
Component:	grub2	Assignee:	Peter Jones <pjones>
Status:	CLOSED ERRATA	QA Contact:	Release Test Team <release-test-team-automation>
Severity:	high	Docs Contact:
Priority:	high
Version:	7.3	CC:	amari, aruizrui, cww, fkrska, javierm, jhlavac, joboyer, jstodola, mkolaja, myamazak, pholica, pjones, qe-baseos-daemons, smoroney, ts
Target Milestone:	rc	Keywords:	FutureFeature
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:	grub2-2.02-0.66.el7	Doc Type:	Enhancement
Doc Text:	Feature: Enable grub2 support to read from XFS filesystems with new filesystem features. Reason: When XFS adds new features, they add a feature flag for each, to tell code reading the filesystem that it needs to either implement those features, or that they're there but safe to ignore. When grub2 reads the filesystem, it needs to know about these. Result: We can continue to be able to boot off of the filesystems created during system installation.	Story Points:	---
Clone Of:	1399487	Environment:
Last Closed:	2018-10-30 11:36:23 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:	1399487
Bug Blocks:	1420851, 1477664, 1571842

Comment 2 Tadas Slotkus 2017-01-27 14:53:50 UTC

Same at https://bugs.centos.org/view.php?id=12733

Comment 5 Peter Jones 2018-06-04 17:48:32 UTC

The patch at https://bugzilla.redhat.com/attachment.cgi?id=1225746 looks correct to me; I don't see why it would cause any errors like "no symbol table".  I suspect that's caused by something unrelated that was hit incidentally in building or deploying test packages.

Comment 8 Jan Stodola 2018-07-19 15:20:44 UTC

Reproduced on RHEL-7.3 GA using both methods described in the bug - using rear and changing the fs UUID.

Retested using the same steps on RHEL-7.6 with grub2-2.02-0.73.el7 and rear-2.4-1.el7 and this issue is not reproducible any more.

Moving to VERIFIED.

Comment 13 errata-xmlrpc 2018-10-30 11:36:23 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.

https://access.redhat.com/errata/RHBA-2018:3264