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 1741830 - network interfaces are not coming up at boot time RHEL 7.6
Summary: network interfaces are not coming up at boot time RHEL 7.6
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: initscripts
Version: 7.6
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: rc
: ---
Assignee: Jan Macku
QA Contact: Daniel Rusek
URL:
Whiteboard:
Depends On:
Blocks: 1743249
TreeView+ depends on / blocked
 
Reported: 2019-08-16 08:09 UTC by Anthony
Modified: 2020-03-31 19:43 UTC (History)
4 users (show)

Fixed In Version: initscripts-9.49.49-1.el7
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 1743249 (view as bug list)
Environment:
Last Closed: 2020-03-31 19:43:04 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
sosreport (19.17 MB, application/x-xz)
2019-08-16 08:09 UTC, Anthony 		no flags Details
View All


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2020:1042 0 None None None 2020-03-31 19:43:19 UTC

Description Anthony 2019-08-16 08:09:13 UTC 
Created attachment 1604307 [details]
sosreport

Description of problem:
Network interfaces are not coming up after installation issues appears to be an issue with unused ports with an  network card (eno1 used , eno2-4 not used)

ifcfg files are empty 

-rw-r--r--. 1 root root 255 Aug  7 15:54 /etc/sysconfig/network-scripts/ifcfg-eno1
-rw-r--r--. 1 root root   0 Aug  9 13:36 /etc/sysconfig/network-scripts/ifcfg-eno2
-rw-r--r--. 1 root root   0 Aug  9 13:36 /etc/sysconfig/network-scripts/ifcfg-eno3


Addionally no udev file is created 

ls -l /etc/udev/rules.d/

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

Workaround is to add device to the ifcfg

[root@ieatrcx3490 ~]# cat /etc/sysconfig/network-scripts/ifcfg-eno4
DEVICE=eno4
[root@ieatrcx3490 ~]# ifup eno4

[root@ieatrcx3490 ~]# cat /etc/sysconfig/network-scripts/ifcfg-eno3
[root@ieatrcx3490 ~]# ifup eno3
ERROR     : [/etc/sysconfig/network-scripts/ifup-eth] Device  does not seem to be present, delaying initialisation.



How reproducible:
All the time 

Steps to Reproduce:
1.No cabled all ports within an network card


Actual results:


Expected results:


Additional info:
Previously issue for this
https://access.redhat.com/solutions/2523931
Has a fix ever being delivered for this ?
Comment 2 Lukáš Nykrýn 2019-08-16 09:04:05 UTC 
I am not sure if I follow. What is this bug about? Isn't the device with the cable brought up? Or is this report just about the "Device  does not seem to be present, delaying initialisation." message?
Comment 3 Anthony 2019-08-16 09:42:25 UTC 
The unused are reporting "Device  does not seem to be present, delaying initialisation." when booting up
Comment 4 Lukáš Nykrýn 2019-08-16 10:10:59 UTC 
Let's move this to initscripts, ifup-eth should probably bail out before calling is_available ${REALDEVICE} if REALDEVICE is empty. Like we do when mac address does not match.

The smallest reproducer is:


[root@ci-vm-10-0-137-110 ~]# modprobe dummy
[root@ci-vm-10-0-137-110 ~]# ip link add dummy0 type dummy #fails on rhel7 since the device is created automagically when the module is loaded, this does not happen on newer systems
RTNETLINK answers: File exists
[root@ci-vm-10-0-137-110 ~]# touch /etc/sysconfig/network-scripts/ifcfg-dummy0
[root@ci-vm-10-0-137-110 ~]# ifup dummy0
ERROR     : [/etc/sysconfig/network-scripts/ifup-eth] Device  does not seem to be present, delaying initialization.

Jan, could you please also try what will happen when there is NetworkManager installed and running in such scenario?
Comment 5 Jan Macku 2019-08-19 10:21:59 UTC 
Thank you Lukáš.

This issue is currently fixed in upstream:
https://github.com/fedora-sysv/initscripts/commit/c060c55bd62a18f5563cc30c894d07b0ec1be497
Comment 6 Jan Macku 2019-08-19 12:19:13 UTC 
This bug will be fixed in RHEL 7.8.
Comment 10 errata-xmlrpc 2020-03-31 19:43:04 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-2020:1042
Note You need to log in before you can comment on or make changes to this bug.