Red Hat Bugzilla – Bug 428445
Installer does not prompt for network information during network-based kickstart.
Last modified: 2008-02-19 10:06:53 EST
Description of problem:
Please note, this is not a duplicate of #401531 :-)
When doing a kickstart installation where the kickstart config is located on a
network resource, the installer does not prompt the installer to supply network
information (hostname, IP, gateway, dns servers etc). This screen is instead
skipped and the only option for the installer is to either provide the ip
information on the boot command line, hard code it into the kickstart file or
write a script executed in %pre to generate the network information.
Version-Release number of selected component (if applicable):
Anaconda included in RHEL 5.1 installer.
Steps to Reproduce:
1. Boot CD #1
2. linux ks=nfs:10.49.6.46:/install/ks/ks-rhel5.cfg
3. Observe system boot, retrieve IP information via DHCP, retrieve kickstart
configuration file (with no %network block in it).
4. Enter into the GUI installer.
5. Observe no network screen is presented to configure network interfaces.
6. Other screens are presented with kickstart defaults intact which can be
overrided by the installer.
I have opened SR 1792462 with RH for this. The way we use kickstart is as a
"defaults" system with our installers being able to easily override any defaults
defined in the kickstart config. We would like to see a return to the behavior
of the RHEL4 installer where all anaconda screens are presented to the installer
-- kickstart defaults intact, but able to override them.
Created attachment 291401 [details]
The screen not present during kickstart installations
Actually it appears that the 'asknetwork' option which I see in Fedora(?) may be
just what we need for this.
I'm not sure if it's available in RHEL 5.1 (will test) -- if not, can we see
I have added this request to my SR as well.
After testing, the 'asknetwork' option does not appear to trigger the Anaconda
GUI network information screen in either Fedora 8 nor in RHEL 5.1.
Created attachment 291413 [details]
Fixes the issue for me.
This patch resolves the issue for me.
This appears to be a duplicate of #401531 if someone would be willing to mark it
*** This bug has been marked as a duplicate of 401531 ***