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 1659137 - ReaR doesn't restore the network configuration when custom interface naming is used
Summary: ReaR doesn't restore the network configuration when custom interface naming i...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: rear
Version: 7.6
Hardware: All
OS: Linux
urgent
medium
Target Milestone: rc
: ---
Assignee: Pavel Cahyna
QA Contact: David Jež
URL:
Whiteboard:
Depends On:
Blocks: 1663222 1663418
TreeView+ depends on / blocked
 
Reported: 2018-12-13 16:35 UTC by Renaud Métrich
Modified: 2019-08-06 13:12 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 1663222 1663418 (view as bug list)
Environment:
Last Closed: 2019-08-06 13:12:05 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github rear rear pull 2004 0 'None' 'closed' 'network: Automatically map device to its new name when device is found on the system with same MAC address but differen... 2019-11-21 17:00:17 UTC
Red Hat Product Errata RHBA-2019:2273 0 None None None 2019-08-06 13:12:31 UTC

Description Renaud Métrich 2018-12-13 16:35:12 UTC 
Description of problem:

When a network interface is not standard (e.g. "ethX", "ensX", etc) but customized (e.g. "my-eth"), ReaR doesn't set up the network interface and this ends up having no network, which is an issue unless DHCP is used.

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

rear-2.4-2.el7.x86_64


How reproducible:

Always


Steps to Reproduce:
1. Set up a system and rename the interface

# cat /etc/sysconfig/network-scripts/ifcfg-first
TYPE="Ethernet"
BOOTPROTO="dhcp"
DEFROUTE="yes"
IPV6INIT="no"
DEVICE="first"
HWADDR="52:54:00:eb:6c:bf"
ONBOOT="yes"

2. Backup the system ("mkrescue" is enough) after configuring ReaR with USE_STATIC_NETWORKING=y

# cat /etc/rear/site.conf
USE_STATIC_NETWORKING=y


3. Try restoring the system


Actual results:

No network interface


Expected results:

Network interface configured


Additional info:

Upstream PR: https://github.com/rear/rear/pull/2004
Comment 2 Pavel Cahyna 2018-12-13 16:54:40 UTC 
(In reply to Renaud Métrich from comment #0)

> Steps to Reproduce:
> 1. Set up a system and rename the interface
> 
> # cat /etc/sysconfig/network-scripts/ifcfg-first
> TYPE="Ethernet"
> BOOTPROTO="dhcp"
> DEFROUTE="yes"
> IPV6INIT="no"
> DEVICE="first"
> HWADDR="52:54:00:eb:6c:bf"
> ONBOOT="yes"

Does this actually rename the interface? I would expect it to create a profile named "first" which still refers to the original interface (eth0 or whatever).
Comment 3 Renaud Métrich 2018-12-14 08:29:07 UTC 
# ls -l /sys/class/net/
total 0
lrwxrwxrwx. 1 root root 0 Dec 14 09:12 first -> ../../devices/pci0000:00/0000:00:03.0/virtio0/net/first
lrwxrwxrwx. 1 root root 0 Dec 14 09:12 lo -> ../../devices/virtual/net/lo
lrwxrwxrwx. 1 root root 0 Dec 14 09:12 second -> ../../devices/pci0000:00/0000:00:04.0/virtio1/net/second
Comment 13 Pavel Cahyna 2019-02-24 18:24:02 UTC 
(In reply to Renaud Métrich from comment #0)
> 1. Set up a system and rename the interface
> 
> # cat /etc/sysconfig/network-scripts/ifcfg-first
> TYPE="Ethernet"
> BOOTPROTO="dhcp"
> DEFROUTE="yes"
> IPV6INIT="no"
> DEVICE="first"
> HWADDR="52:54:00:eb:6c:bf"
> ONBOOT="yes"
> 
> 
> 3. Try restoring the system
> 
> 
> Actual results:
> 
> No network interface
> 
> 
> Expected results:
> 
> Network interface configured

Renaud,

should one expect the interface configured to be properly named ("first") or to have the original name ("eth0" or whatever)? When we try this, we get a proper IP address configured on the interface, but it is not renamed properly.
Comment 14 Renaud Métrich 2019-02-26 12:38:10 UTC 
Interface will not be renamed, hence "eth0" is expected, but you shouldn't get any IP address if /etc/rear/local.conf contains "USE_STATIC_NETWORKING=y"

With the fix and USE_STATIC_NETWORKING=y, /etc/scripts/system-setup.d/60-network-devices.sh 's content gets renamed from "first" to "ethX"
Comment 15 Pavel Cahyna 2019-02-26 13:04:53 UTC 
(In reply to Renaud Métrich from comment #14)
> Interface will not be renamed, hence "eth0" is expected, but you shouldn't
> get any IP address if /etc/rear/local.conf contains "USE_STATIC_NETWORKING=y"

It was meant "before the fix, you shouldn't get any IP address". After the fix you should of course.
Comment 19 errata-xmlrpc 2019-08-06 13:12:05 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-2019:2273
Note You need to log in before you can comment on or make changes to this bug.