Bug 186292 - Anaconda wants console input r.e ethernet choice
Summary: Anaconda wants console input r.e ethernet choice
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Enterprise Linux 4
Classification: Red Hat
Component: anaconda
Version: 4.0
Hardware: i686
OS: Linux
medium
medium
Target Milestone: ---
: ---
Assignee: Anaconda Maintenance Team
QA Contact: Mike McLean
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2006-03-22 18:59 UTC by Erik Karl Sorgatz
Modified: 2007-11-30 22:07 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2007-08-24 21:49:47 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
MAXimum install of RHEL4 (1.34 KB, application/octet-stream)
2006-03-22 18:59 UTC, Erik Karl Sorgatz
no flags Details

Description Erik Karl Sorgatz 2006-03-22 18:59:15 UTC
Attempting headless kickstart, using NFS/bootp/dhcp from one HP DL360 server
(with RHEL4 fully installed and configured) to another HP DL360. PXEboot
happens, the NFS mounted isos are accessed as is the ks.cfg;  but Anaconda 
absolutely INSISTS on having a console input from the kickstart target machine
to confirm the selection of eth0 vs eth1 for the install. WHY?! I have nothing
plugged into ther eth1 port, as opposed to the eth0 which is plugged into a
Netgear switch (lines high and active..) This means I have to answer this query
for each and every machine I want to install - which means dragging a KVM crash
cart around the room. <please see attached ks.cfg> 


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


How reproducible:


Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:

Comment 1 Erik Karl Sorgatz 2006-03-22 18:59:15 UTC
Created attachment 126495 [details]
MAXimum install of RHEL4

Comment 2 Chris Lumens 2006-03-23 15:05:46 UTC
Try adding ksdevice=eth0 to your boot parameters.

Comment 4 Red Hat Bugzilla 2007-06-12 03:07:24 UTC
requested by Jams Antill


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