Bug 906470 - network initialization takes 11min before first installation screen
Summary: network initialization takes 11min before first installation screen
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: anaconda
Version: 18
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Radek Vykydal
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-01-31 17:03 UTC by Martin Wilck
Modified: 2014-02-05 18:44 UTC (History)
5 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2014-02-05 18:44:55 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
/tmp/syslog (166.73 KB, text/plain)
2013-01-31 17:03 UTC, Martin Wilck
no flags Details

Description Martin Wilck 2013-01-31 17:03:24 UTC
Created attachment 691085 [details]
/tmp/syslog

Description of problem:
Installing F18 via PXE on a server with 8 network interfaces, it takes ~11min minutes before anything interesting happens.

Version-Release number of selected component (if applicable):
Fedora 18 GA

How reproducible:
Always

Steps to Reproduce:
1. Install on RX300S7 with PXE
  
Actual results:
First useful installer screen after >10min

Expected results:
Installer starts when the first interface is found that successfully connects to the configured installation source (HTTP in my case). In the scenario at hand, the first interface is p2p1, after 11s. The "correct" PXE interface is em1 which is activated after ~140s. This server has a bonding setup (which is not available in anaconda AFAIK), so there are actually several interfaces connected to the same LAN segment. 

Additional info:
A suppose a workaround would be using the "ip=" boot option. But RHEL6 features a screen where the network interfaces to activate can be selected, even offering to identify the interface. That would be highly desirable.

Comment 1 Martin Wilck 2013-01-31 17:24:46 UTC
Perhaps a configuration error; our PXE server had added the "ip=dhcp" boot option automatically. Removing that and manually entering "ip=em1:dchp" actually speeds up things a lot. Not as obvious and user-friendly as the RHEL6 menu, though.

Just removing "ip=dhcp" has no positive effect, because "ip=dhcp" is the default, and will bring up all interfaces.

Comment 2 Fedora End Of Life 2013-12-21 11:02:30 UTC
This message is a reminder that Fedora 18 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 18. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '18'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 18's end of life.

Thank you for reporting this issue and we are sorry that we may not be 
able to fix it before Fedora 18 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior to Fedora 18's end of life.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 3 Fedora End Of Life 2014-02-05 18:44:55 UTC
Fedora 18 changed to end-of-life (EOL) status on 2014-01-14. Fedora 18 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.


Note You need to log in before you can comment on or make changes to this bug.