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


How reproducible:
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.

Actual results:
No working routing and also no working network interface while trying to recover.


Expected results:
A working network connection to recover for example over TSM or other network-based backup tools.


Additional info:
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.

https://rhn.redhat.com/errata/RHBA-2016-2208.html