Bug 1390855

Summary: Recover from rear does not work in RHEL 7.3 beta while it works well in RHEL 7.2
Product: Red Hat Enterprise Linux 7 Reporter: JongYoung Moon <jmoon>
Component: rearAssignee: Jakub Mazanek <jmazanek>
Status: CLOSED ERRATA QA Contact: Tereza Cerna <tcerna>
Severity: high Docs Contact:
Priority: unspecified    
Version: 7.3CC: cww, gratien.dhaese, jmazanek, khuh, mmatsuya, ovasik, phracek, tcerna
Target Milestone: rc   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-08-01 22:19:55 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:    
Bug Blocks: 1298243, 1393870, 1400961    
Attachments:
Description Flags
Full log of recover failure from running "rear -v -d recover" none

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