Bug 1784358

Summary: no iproute2 in initrd when using "network-manager" module in dracut
Product: Red Hat Enterprise Linux 8 Reporter: Thomas Haller <thaller>
Component: dracutAssignee: Lukáš Nykrýn <lnykryn>
Status: CLOSED ERRATA QA Contact: Frantisek Sumsal <fsumsal>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 8.2CC: dhorak, dracut-maint-list, fsumsal, rvykydal
Target Milestone: rc   
Target Release: 8.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-04-28 16:06:04 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Thomas Haller 2019-12-17 10:16:45 UTC
See
https://bugzilla.redhat.com/show_bug.cgi?id=1727904#c13
https://bugzilla.redhat.com/show_bug.cgi?id=1774438#c20


when using the network-manager dracut module, the generated initrd no longer contains iproute2. Lacking such a fundamental tool may be inconvenient for debugging.

The network-manager module itself doesn't need it, but it should be possible (at least as opt-in) to include iproute2 in initrd.

Comment 1 Dan Horák 2019-12-17 10:52:11 UTC
Yup, lack of /usr/sbin/ip in the initrd makes debugging of network setup related issues painful. And network installation the primary installation method used on s390x.

Comment 2 Radek Vykydal 2020-01-06 16:55:42 UTC
For the reference, see also bug 1769825 where we are going to use ip tool (at least for now) to learn IP address for generated kickstart file name.

Comment 3 Thomas Haller 2020-01-14 08:19:04 UTC
fixed upstream by https://github.com/dracutdevs/dracut/pull/702

Comment 7 errata-xmlrpc 2020-04-28 16:06: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:1760