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 1331276 - Start of network fails when no DEVICE is defined in the ifcfg-ethx file and NM disabled
Summary: Start of network fails when no DEVICE is defined in the ifcfg-ethx file and N...
Keywords:
Status: CLOSED WORKSFORME
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: dracut
Version: 7.2
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Lukáš Nykrýn
QA Contact: Release Test Team
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-04-28 07:50 UTC by David Caro
Modified: 2019-10-24 17:25 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-10-24 15:17:46 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description David Caro 2016-04-28 07:50:30 UTC 
Description of problem:
When disabling network manager, if there were no 'DEVICE' options defined in the /etc/sysconfig/network-scripts/ifcfg-ethX files, the network fails to start 

Version-Release number of selected component (if applicable):
# cat /etc/redhat-release 
CentOS Linux release 7.2.1511 (Core) 

# rpm -qf /etc/sysconfig/network-scripts/ifup-eth
initscripts-9.49.30-1.el7.x86_64


How reproducible:
Get a CentOS 7.2 basic installation (I used virt-builder centos-7.2), disable NetworkManager, and run 'service network restart'

Steps to Reproduce:
1.
2.
3.

Actual results:
It fails complaining that the 'device' does not seem to be present

Expected results:
It should work correctly

Additional info:
Apr 27 10:46:18 lago_basic_suite_master_host0 systemd[1]: Stopping LSB: Bring up/down networking...
-- Subject: Unit network.service has begun shutting down
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- Unit network.service has begun shutting down.
Apr 27 10:46:18 lago_basic_suite_master_host0 network[2403]: Shutting down interface eth0:  ERROR    : [ipv6_test_device_status] Missing parameter 'device' (arg 1)
Apr 27 10:46:18 lago_basic_suite_master_host0 ipv6_test_device_status[2444]: Missing parameter 'device' (arg 1)
Apr 27 10:46:18 lago_basic_suite_master_host0 network[2403]: [  OK  ]
Apr 27 10:46:18 lago_basic_suite_master_host0 network[2403]: Shutting down loopback interface:  [  OK  ]
Apr 27 10:46:18 lago_basic_suite_master_host0 systemd[1]: Starting LSB: Bring up/down networking...
-- Subject: Unit network.service has begun start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- Unit network.service has begun starting up.
Apr 27 10:46:18 lago_basic_suite_master_host0 network[2549]: Bringing up loopback interface:  [  OK  ]
Apr 27 10:46:18 lago_basic_suite_master_host0 network[2549]: Bringing up interface eth0:  ERROR    : [/etc/sysconfig/network-scripts/ifup-eth] Device  does not seem to be present, delaying initialization.
Apr 27 10:46:18 lago_basic_suite_master_host0 /etc/sysconfig/network-scripts/ifup-eth[2671]: Device  does not seem to be present, delaying initialization.
Apr 27 10:46:18 lago_basic_suite_master_host0 network[2549]: [FAILED]
Apr 27 10:46:18 lago_basic_suite_master_host0 systemd[1]: network.service: control process exited, code=exited status=1
Apr 27 10:46:18 lago_basic_suite_master_host0 systemd[1]: Failed to start LSB: Bring up/down networking.
-- Subject: Unit network.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- Unit network.service has failed.
-- 
-- The result is failed.
Apr 27 10:46:18 lago_basic_suite_master_host0 systemd[1]: Unit network.service entered failed state.
Apr 27 10:46:18 lago_basic_suite_master_host0 systemd[1]: network.service failed.


The /etc/sysconfig/network-scripts/ifcfg-eth0 file that gets generated by dracut:

# Generated by dracut initrd
NAME="eth0"
ONBOOT=yes
NETBOOT=yes
UUID="b26dbb85-536c-4a01-86fc-57bb01cca298"
IPV6INIT=yes
BOOTPROTO=dhcp
TYPE=Ethernet
DEFROUTE=yes
IPV4_FAILURE_FATAL=no
IPV6_AUTOCONF=yes
IPV6_DEFROUTE=yes
IPV6_FAILURE_FATAL=no
PEERDNS=yes
PEERROUTES=yes
IPV6_PEERDNS=yes
IPV6_PEERROUTES=yes
Comment 2 Lukáš Nykrýn 2016-05-30 12:14:27 UTC 
Initscripts need either DEVICE or HWADDR.
Comment 5 Jan Macku 2019-10-24 15:17:46 UTC 
I'm not able to reproduce this issue. It works in current release of dracut.

If it's still issue for you please send us logs with set parameter "rd.break" on kernel cmd.
Comment 6 Lukáš Nykrýn 2019-10-24 17:25:24 UTC 
(In reply to Jan Macku from comment #5)
> I'm not able to reproduce this issue. It works in current release of dracut.
> 
> If it's still issue for you please send us logs with set parameter
> "rd.break" on kernel cmd.

And also please put there rd.debug
Note You need to log in before you can comment on or make changes to this bug.