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 1390855 - Recover from rear does not work in RHEL 7.3 beta while it works well in RHEL 7.2
Summary: Recover from rear does not work in RHEL 7.3 beta while it works well in RHEL 7.2
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: rear
Version: 7.3
Hardware: All
OS: Linux
unspecified
high
Target Milestone: rc
: ---
Assignee: Jakub Mazanek
QA Contact: Tereza Cerna
URL:
Whiteboard:
Depends On:
Blocks: 1298243 1393870 1400961
TreeView+ depends on / blocked
 
Reported: 2016-11-02 06:21 UTC by JongYoung Moon
Modified: 2020-02-14 18:04 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-08-01 22:19:55 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
Full log of recover failure from running "rear -v -d recover" (610.71 KB, text/plain)
2016-11-02 06:21 UTC, JongYoung Moon
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2017:2052 0 normal SHIPPED_LIVE rear bug fix update 2017-08-01 19:33:49 UTC

Description JongYoung Moon 2016-11-02 06:21:28 UTC
Created attachment 1216361 [details]
Full log of recover failure from running "rear -v -d recover"

Description of problem:
- Recover from rear does not work normally in RHEL 7.3 beta while it works well in
RHEL 7.2.

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

How reproducible:
- It can be reproduced on any VM environments such as VirtualBox, virt-manager and so on


Steps to Reproduce:

In my test case, it could be reproduced in RHEL VM of VirtualBox on MacOS.

01. Created VM
02. Installed RHEL 7.3 Beta
03. Configured local repository after mount ISO installation image.
04. Install rear package
   $ yum install rear

05. Configure /etc/reare/local.conf

    OUTPUT=ISO
    OUTPUT_URL=file:///backup
    BACKUP=NETFS
    BACKUP_URL=nfs://192.168.0.XX/backup


06. Created backup
    $ rear -d -D mkbackup 

07. Confirmed if backup is created.
    We confirmed if backup data and ISO image are created in local /backup directory and backup directory in NFS Server.

08. Modified disk so that it's not bootable.
    $ shred /dev/sda

09. Confirmed that it's not bootable after reboot.

10. Booted with ISO image created at step 7)

11. Performing recovery job after selecting auto-recovery.

12. Confirmed that partition table and filesystems are recovered.

13. Found that installing bootloader is failed through error messages we uploaded on the case.

14. Confirmed that booting from local disk is failed.


Actual results:

With the following error logs, recover from rear ( rear -v d recover ) is failed.

RedHatEnterpriseServer/7 on Linux-i386 (based on Fedora/7/i386)
there is no code to install a boot loader on the recovered system or the code
that we have failed to install the boot loader correctly.

Please contribute this code to the Relax-and-Recover project. To do so
please take a look at the scripts in /usr/share/rear/finalize,
for an example you can use the script for Fedora (and RHEL/CentOS/SL) in
/usr/share/rear/finalize/Linux-i386/21_install_grub.sh or
/usr/share/rear/finalize/Linux-i386/22_install_grub2.sh

--------------------  ATTENTION ATTENTION ATTENTION -------------------
|                                                                     |
|          IF YOU DO NOT INSTALL A BOOT LOADER MANUALLY,              |
|                                                                     |
|          THEN YOUR SYSTEM WILL N O T BE ABLE TO BOOT !              |
|                                                                     |
-----------------------------------------------------------------------


Expected results:

I expect that recover from rear would be worked well.


Additional info:
Full log of recover failure could seen at rear-rhel73rc2.log attached on this BZ.

Comment 14 Gratien D'haese 2017-03-01 11:13:24 UTC
This BZ has been fixed in ReaR v2.00
See https://github.com/rear/rear/issues/1174 for more details.

Comment 17 Tereza Cerna 2017-06-22 11:31:38 UTC
I'm not able to reproduce this bug. 

Rear is working in new version rear-2.00-2.el7. I did several attempts and it is possible to do recover. Related bug BZ#1399487 were verified and works correctly.

So... Verified as SanityOnly

Comment 18 errata-xmlrpc 2017-08-01 22:19:55 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-2017:2052


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