Red Hat Bugzilla – Bug 1283930
ReaR recovery over teaming interface will not work
Last modified: 2016-11-03 20:28:58 EDT
Description of problem:
On RHEL 7.2 with rear-1.17.2-1.el7.noarch a recovery over a configured teaming interface and a network-recovery-service will probably not work due missing routing information.
Version-Release number of selected component (if applicable):
rear-1.17.2-1.el7.noarch on RHEL 7.2
Create a backup on a system with a teaming-interface as default interface and try to recover from this iso over a network-backup-service as e.g. TSM.
Steps to Reproduce:
1. Create a teaming interface instead of eth0...
2. rear mkrescue
3. Boot from ISO and try to restore.
No working routing and also no working network interface while trying to recover.
A working network connection to recover for example over TSM or other network-based backup tools.
I made a workaround on git for this: https://github.com/rear/rear/pull/662
I simplified the function that all ip-addresses and routing-entries of a teaming-interface will be attached to its first available teaming-member (output by teamdctl).
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.