Bug 1396269 - RHEL-7.3 fails to install on a specific Dell server R730 -netdev49
Summary: RHEL-7.3 fails to install on a specific Dell server R730 -netdev49
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: dracut
Version: 7.3
Hardware: x86_64
OS: Unspecified
urgent
urgent
Target Milestone: rc
: ---
Assignee: Lukáš Nykrýn
QA Contact: Release Test Team
URL:
Whiteboard:
Depends On:
Blocks: 1380361
TreeView+ depends on / blocked
 
Reported: 2016-11-17 20:04 UTC by Aniss Loughlam
Modified: 2017-03-01 16:54 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-03-01 16:54:29 UTC
Target Upstream Version:

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Comment 8 Aniss Loughlam 2017-01-20 22:21:42 UTC 
any updates
Comment 11 Lukáš Nykrýn 2017-02-20 16:49:14 UTC 
Maybe try to put rd.net.timeout.carrier=30 on your kernel cmdline.
Comment 12 Anthony Gialluca 2017-03-01 14:43:19 UTC 
I had responded to a bugzilla email (below) but it does not appear to have been put in this BZ.  The recommended fix did in fact work. Please feel free to resolve/close this BZ.

-------- Forwarded Message --------
Subject: 	Re: [Bug 1396269] RHEL-7.3 fails to install on a specific Dell server R730 -netdev49
Date: 	Wed, 22 Feb 2017 10:48:22 -0500
From: 	Anthony Gialluca <agialluc>
Reply-To: 	agialluc
Organization: 	Red Hat
To: 	bugzilla


Lukáš,

I have to admit that this surprised me, using
'rd.net.timeout.carrier=30' seems to have fixed this issue [1]. I'll
have to look into what rd.net.timeout.carrier is doing to satisfy my
curiosity.

However, Please feel free to resolve/close this issue at your convenience.

Thanks for you help,
-Tony

RE:
[1] https://beaker.engineering.redhat.com/jobs/1729723
Comment 13 Lukáš Nykrýn 2017-03-01 16:54:29 UTC 
I am glad that it helped. I guess there might be some hw issue, that it take so long to get a carrier
Note You need to log in before you can comment on or make changes to this bug.