Bug 694653 - Cannot manually configure network for network install
Summary: Cannot manually configure network for network install
Keywords:
Status: CLOSED WORKSFORME
Alias: None
Product: Fedora
Classification: Fedora
Component: anaconda
Version: 14
Hardware: i386
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: Radek Vykydal
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-04-07 20:52 UTC by Tom Trebisky
Modified: 2011-06-23 09:49 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-06-23 09:49:21 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Tom Trebisky 2011-04-07 20:52:36 UTC
Description of problem:

I am assuming anything involving the installer is anaconda.

I cannot manually configure ipv4 parameters to do a network install.
The workaround is to setup a DHCP entry to do the install and then
once linux is installed redo the network setup to be static

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

I am using the image
fedora/releases/14/Fedora/i386/iso/Fedora-14-i386-netinst.iso
burned onto a CD

How reproducible:

Every time I try it

Steps to Reproduce:
1. Boot the CD and begin to install a new system
2. A screen asks for the hostname, click the Configure Network button at
   the lower left
3. In the dialogs that follow, select eth0, edit, the click the ipv4 settings
   tab, within that tab change from the default of DHCP to Manual and voila,
   the Apply button greys out and it is impossible to make any settings.
   At least I haven't figured out how to do so without the Apply button.
  
Actual results:


Expected results:


Additional info:

Comment 1 Chris Lumens 2011-04-07 20:59:19 UTC
F15 beta is just about to be released.  Please retest with that or at least with F15 alpha.  Lots of networking changes have gone into anaconda since F14.

Comment 2 Tom Trebisky 2011-04-08 01:07:31 UTC
OK, I am gonna give you a two part response.  I did the workaround I mentioned using DHCP since I had easy access to a DHCP server and got my install going, but was annoyed that it did not ask me the URL of the repository to install from (we have a local mirror and it would have been much faster to use that).  Then I remembered that there was a trick, using the "askmethod" kernel option, and verified that this still existed (I haven't used it since fedora 11).  It does exist as I remember it on the fedora 14 CD and has a different (and apparently functional) dialog to enter ipv4 information.  I mention all this because this would have been a different workaround from setting up entries in a DHCP server.

Then I dug around looking for Fedora 15 beta.  All I could find was Fedora 15 alpha (but would be happy to test the beta if you tell me where to find it).
I burned the 15 alpha network install CD and booted it.  To my utter amazement it seems to be a delightful regression, no graphical interface (with the bug originally reported), it seems to run a non-graphical interface almost but not quite identical to the secret dialog accessed previously by the "askmethod" kernel option.  This dialog allows me to enter the network configuration and seems to work fine, so YES, this fixes my problem.  After this it jumps to a graphical interface and seems to be off to the races, but I interrupted it and did not allow it to complete the 15 alpha install.

I then verified that appending the secret "askmethod" switch still works
(and it does) with the 15 alpha network install CD.
I will make a plea here: I think the option to specify the URL to install from should be more mainstream. Around here we certainly do a lot of installs from a local mirror and they both go faster and do not burden public repositories when done that way.

And thanks for the help and quick attention.

Comment 3 Radek Vykydal 2011-06-23 09:49:21 UTC
I tested with F14 netinst that after adding static configuration (Add in Addresses) the Apply button becomes sensitive again.

Please note (which is not matter of this report but you may hit it in following steps) that in this UI stage ("Configure Network" button) you have to check "Connect automatically" so that the device is also activated in installer (not only configured for target system).


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