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 1371858

Summary: [RFE] Dracut timeout 60 seconds per interface when it can't find a route to the interface's gateway
Product: Red Hat Enterprise Linux 7 Reporter: Supreet <srandhaw>
Component: dracutAssignee: Lukáš Nykrýn <lnykryn>
Status: CLOSED CANTFIX QA Contact: Release Test Team <release-test-team-automation>
Severity: medium Docs Contact:
Priority: medium    
Version: 7.2CC: dereks, dracut-maint-list, harald, jstodola, michael.facciani
Target Milestone: rcKeywords: FutureFeature
Target Release: 7.3   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-11-02 12:30:01 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:
Bug Depends On:    
Bug Blocks: 1298243, 1420851, 1466365    

Description Supreet 2016-08-31 09:48:58 UTC 
Description of problem:
When configuring a system to use the ip= boot option the system will timeout after 60 seconds per interface when it can't find the provided gateway.

dracut's ip= is using arping and waits 60 seconds for a gateway to respond.

https://github.com/dracutdevs/dracut/blob/RHEL-7/modules.d/40network/net-lib.sh#L168

This setting should be something that's configurable via an additional boot option.  When configuring multiple interfaces this way on a network less machine causes an excessive amount of waiting. 3+ minutes.


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

Additional info:
 Upstream patch : 

https://github.com/dracutdevs/dracut/blob/RHEL-7/modules.d/40network/net-lib.sh#L168
Comment 4 Lukáš Nykrýn 2017-11-02 12:30:01 UTC 
Unfortunately the patch in upstream dracut uses arping2 which is not available in rhel7.
Comment 5 Derek Schrock 2017-12-07 13:11:57 UTC 
https://github.com/dracutdevs/dracut master uses arping2 however it does fall back to arping if arping2 isn't found.   Is the patch you're referencing something else?

https://github.com/dracutdevs/dracut/blob/master/modules.d/40network/net-lib.sh#L174 

But the point is both are hard coded to wait 60 seconds (or arping2 60 counts). This 60 seconds wait should be a passable value and if not passed defaulted to 60 seconds. arping ... -w 60