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.
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.