This bug has been migrated to another issue tracking site. It has been closed here and may no longer be being monitored.

If you would like to get updates for this issue, or to participate in it, you may do so at Red Hat Issue Tracker .
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 1989150 - rear doesn't include grub2-* tools when having a rogue file in /boot
Summary: rear doesn't include grub2-* tools when having a rogue file in /boot
Keywords:
Status: CLOSED MIGRATED
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: rear
Version: 8.4
Hardware: All
OS: Linux
high
high
Target Milestone: rc
: ---
Assignee: Pavel Cahyna
QA Contact: Jakub Haruda
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-08-02 14:27 UTC by Renaud Métrich
Modified: 2024-10-01 19:07 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: No Doc Update
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-09-21 23:40:36 UTC
Type: Bug
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker   RHEL-6954 0 None Migrated None 2023-09-21 23:39:22 UTC
Red Hat Issue Tracker RHELPLAN-91886 0 None None None 2021-08-02 14:29:04 UTC

Description Renaud Métrich 2021-08-02 14:27:26 UTC 
This bug was initially created as a copy of Bug #1989140

I am copying this bug because: 

Also applies.


Description of problem:

When there is a rogue file e.g. /boot/grub2XXX, ReaR doesn't include the grub2-* binaries, making it impossible to recover a system.


Version-Release number of selected component (if applicable):

rear-2.4, maybe Upstream, didn't check

How reproducible:

Always

Steps to Reproduce:
1. Create a rogue file

  # touch /boot/grub2FAIL

2. Create a rescue in debug

  # rear -dD mkrescue

3. Check the rescue content: no /bin/grub2-* files embedded!

  # ll /tmp/rear.BIwW0X1HU7trKny/rootfs/bin/grub2*

Actual results:

ls: cannot access '/tmp/rear.BIwW0X1HU7trKny/rootfs/bin/grub2*': No such file or directory

Expected results:

Files there

Additional info:

In the log, we can see that the script /usr/share/rear/prep/GNU/Linux/300_include_grub_tools.sh is kinda stupid because it checks for /boot/grub* files.

Due to the rogue file, the name being returned is "/boot/grub2 /boot/grub2FAIL" which makes ReaR consider it's not valid and expects "/boot/grub" to exist.

Due to not existing, it doesn't include the binaries:

+ source /usr/share/rear/prep/GNU/Linux/300_include_grub_tools.sh
++ test -d /var/lib/rear/recovery
+++ echo -n /boot/grub2 /boot/grub2FAIL
++ local 'grubdir=/boot/grub2 /boot/grub2FAIL'
++ test -d '/boot/grub2 /boot/grub2FAIL'
++ grubdir=/boot/grub
++ has_binary grub-probe
++ for bin in $@
++ type grub-probe
/usr/share/rear/lib/_input-output-functions.sh: line 331: type: grub-probe: not found
++ return 1
++ has_binary grub2-probe
++ for bin in $@
++ type grub2-probe
++ return 0
++ grub2-probe -t device /boot/grub
++ return 0

--> grub2-probe fails due to checking for /boot/grub which doesn't exist, so rest of the script is not executed.
Comment 1 Pavel Cahyna 2021-09-21 16:54:38 UTC 
Thanks for the analysis, I will investigate whether a more reliable check can be implemented.
Comment 4 RHEL Program Management 2023-09-21 23:35:29 UTC 
Issue migration from Bugzilla to Jira is in process at this time. This will be the last message in Jira copied from the Bugzilla bug.
Comment 5 RHEL Program Management 2023-09-21 23:40:36 UTC 
This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there.

Due to differences in account names between systems, some fields were not replicated.  Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information.

To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "RHEL-" followed by an integer.  You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like:

"Bugzilla Bug" = 1234567

In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information.
Note You need to log in before you can comment on or make changes to this bug.