Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

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 1369016

Summary:	systemd starts the network script before systemd-udev finishes ethernet interfaces renaming
Product:	Red Hat Enterprise Linux 7	Reporter:	Marcel Kolaja <mkolaja>
Component:	initscripts	Assignee:	initscripts Maintenance Team <initscripts-maint-list>
Status:	CLOSED ERRATA	QA Contact:	Leos Pol <lpol>
Severity:	high	Docs Contact:
Priority:	high
Version:	7.2	CC:	deekej, fkrska, jscotka, kcleveng, knoha, lpol, mkolaja, mnavrati, rmanes, zpytela
Target Milestone:	rc	Keywords:	ZStream
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	initscripts-9.49.30-1.el7_2.4	Doc Type:	Bug Fix
Doc Text:	Previously, the systemd service executed the network script that starts networking before the systemd-udev service finished renaming ethernet interfaces. As a consequence, networking did not work because the required interface was not found, and the following error message occurred: network: Bringing up interface em1: ERROR : [/etc/sysconfig/network-scripts/ifup-eth] Device em1 does not seem to be present, delaying initialization. A patch has been applied to fix this bug, and networking no longer fails to start due to the described problem.	Story Points:	---
Clone Of:	1339648	Environment:
Last Closed:	2016-11-09 17:16:05 UTC	Type:	---
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:	1339648
Bug Blocks:

Description Marcel Kolaja 2016-08-22 10:42:18 UTC

This bug has been copied from bug #1339648 and has been proposed
to be backported to 7.2 z-stream (EUS).

Comment 11 Leos Pol 2016-09-06 09:19:44 UTC

OLD: initscripts-9.49.30-1.el7

# echo -e "DEVICE=test\nDEVTIMEOUT=10" > /etc/sysconfig/network-scripts/ifcfg-test
# time ifup test
ERROR    : [/etc/sysconfig/network-scripts/ifup-eth] Device test does not seem to be present, delaying initialization.

real	0m0.121s
user	0m0.048s
sys	0m0.070s

NEW: initscripts-9.49.30-1.el7_2.4

# echo -e "DEVICE=test\nDEVTIMEOUT=10" > /etc/sysconfig/network-scripts/ifcfg-test
# time ifup test
ERROR    : [/etc/sysconfig/network-scripts/ifup-eth] Device test does not seem to be present, delaying initialization.

real	0m10.132s
user	0m0.059s
sys	0m0.069s

New version waits for device appearance for DEVTIMEOUT, which fixing this issue.

Comment 18 errata-xmlrpc 2016-11-09 17:16: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://rhn.redhat.com/errata/RHBA-2016-2682.html