Bug 174299 - Anaconda unable to find ks.cfg on NFS Server
Anaconda unable to find ks.cfg on NFS Server
Status: CLOSED NOTABUG
Product: Red Hat Enterprise Linux 4
Classification: Red Hat
Component: anaconda (Show other bugs)
4.0
i386 Linux
medium Severity high
: ---
: ---
Assigned To: Jeremy Katz
Mike McLean
None
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2005-11-27 09:46 EST by Iradj Atchatchloui
Modified: 2007-11-30 17:07 EST (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2005-11-27 12:52:34 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Iradj Atchatchloui 2005-11-27 09:46:59 EST
From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; X11; Linux i686) Opera 7.23  [en]

Description of problem:
o have been Kickstarting with RedHat since Veriosn 7.2 as:
- boot CD with ks.cfg on it
- no interactive actions on installations at all:
        - eth0, no PXE, No DHCP
        - put boot CD in the machine
        - after 20 Minutes I'm done
- source installation files are on NFS Server

o My attempts on having ks.cfg file either on NFS Server has allways failed. 
Anaconda aboart the installation with messages like:
"Error opening kickstart file /tmp/ks.cfg. No such file or directory"
"failed to copy ks.cfg to /tmp/ks.cfg"

- I have tried to handle this with putting the appropriate strings in "isolinux.
cfg", examples:

default ks
append ks=nfs:192.168.172.91:/var/data/os/linux/redhat/kickstart/ks.cfg 
initrd=initrd.img

default linux
append ksdevice=eth0 console=tty0 console=ttyS0,38400 load_ramdisk=1 
initrd=initrd.img network ks=nfs:192.168.172.
91/var/data/sdavg/dvdimglv/rhes40-rpms/ks/ks.cfg

default linux
append ks=nfs:192.168.172.91/var/data/sdavg/dvdimglv/rhes40-rpms/ks/ks.cfg 
initrd=initrd.img

default linux
append ksdevice=eth0 console=tty0 console=ttyS0,38400 load_ramdisk=1 
initrd=initrd.img network ks=nfs:192.168.172.
91/var/data/sdavg/dvdimglv/rhes40-rpms/ks/ks.cfg

Well, I don't know whether I'm doing somthing wrong or this is a bug.


Version-Release number of selected component (if applicable):
rpm-4.3.3-7 / kernel-2.6.9-5.EL

How reproducible:
Always

Steps to Reproduce:
See Description  

Actual Results:  Aboart Installation

Expected Results:  Succsessfull Installation as ks.cfg on boot CD

Additional info:

None
Comment 1 Iradj Atchatchloui 2005-11-27 09:48:45 EST
NOTE:
Wrong:192.168.172.
Comment 2 Iradj Atchatchloui 2005-11-27 09:55:02 EST
NOTE: Sure IP got no dot at the END.
FALLS:192.168.172.91.
TRUE: 192.168.172.91
Comment 3 Jeremy Katz 2005-11-27 12:52:34 EST
You need a colon between the ip and the path, eg
ks=nfs:192.168.1.1:/vol/vol1/foo
Comment 4 Iradj Atchatchloui 2005-11-27 15:07:59 EST
(In reply to comment #3)
> You need a colon between the ip and the path, eg
> ks=nfs:192.168.1.1:/vol/vol1/foo

As you see, in one of my examples I got the colon as you say:
append ks=nfs:192.168.172.91:/var/data/os/linux/redhat/kickstart/ks.cfg 
initrd=initrd.img

Also with this string I got the same Anaconda failure as with other examples.
I would appriciate if you'd send me an working expample of "isolinux.cfg"

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