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.

any updates

Maybe try to put rd.net.timeout.carrier=30 on your kernel cmdline.

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

I am glad that it helped. I guess there might be some hw issue, that it take so long to get a carrier