Bug 110609 - redhat-config-netboot/pxeboot: Does not include specified kickstart file location in pxelinux.cfg/<host_config_file>
Summary: redhat-config-netboot/pxeboot: Does not include specified kickstart file loca...
Status: CLOSED RAWHIDE
Alias: None
Product: Red Hat Enterprise Linux 3
Classification: Red Hat
Component: redhat-config-netboot (Show other bugs)
(Show other bugs)
Version: 3.0
Hardware: i686 Linux
medium
medium
Target Milestone: ---
Assignee: Daniel Walsh
QA Contact:
URL:
Whiteboard:
Keywords:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2003-11-21 18:22 UTC by gary
Modified: 2007-11-30 22:06 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2003-11-21 19:25:36 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

Description gary 2003-11-21 18:22:49 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.5b)
Gecko/20030812 Mozilla Firebird/0.6.1+

Description of problem:
* Using either the redhat-config-network GUI or the pxeboot CLI, the
kickstart file location information is not saved in the resulting
configuration file in /tftpboot/linux-install/pxelinux.cfg/.  

*If you go to create a new host in the GUI (File->New), you can
specify the location of the kickstart file in the field "Kickstart
File."  With the CLI, you use the -K option to specify the location of
the kickstart file.

* Using the following command line (having previously configured the
"rhel-3-as" Operating System description):

pxeboot -a -K ks.cfg -r 10000 -s -O rhel-3-as 192.168.1.12

* Will create the following output in
/tftpboot/linux-install/pxelinux.cfg/C0A8010C:

===== START OUTPUT =====

default rhel-3-as

label rhel-3-as
    kernel rhel-3-as/vmlinuz
    append initrd=rhel-3-as/initrd.img console=ttyS0  ramdisk_size=10000

===== END OUTPUT =====

* Note that there is no mention of the ks.cfg file.
* In /usr/share/redhat-config-netboot/pxeboot.py, line 181 assembles
the "append" line seen above:

            appendLine = "    append initrd=%s/initrd.img %s %s %s " %
(self.__getLabel(),
self.__getConsoleString(),self.__getKickstartString(),self.__getRamdiskString())

* Above, you see the function self.__getKickstartString() being
called.  The definition for this function starts on line 116 of
pxeboot.py:

    def __getKickstartString(self):
        return ""

* As you can see, the function returns an empty string.

* I hope the above informaiton is helpful.  Please contact me at
gary@umsl.edu if you need further information.



Version-Release number of selected component (if applicable):
redhat-config-netboot-0.1.1-19

How reproducible:
Always

Steps to Reproduce:
1.Type: pxeboot -a -K ks.cfg -r 10000 -s -O rhel-3-as 192.168.1.12
2.Type: cat /tftpboot/linux-install/pxelinux.cfg/C0A8010C
3.Notice there is no mention of ks.cfg in
/tftpboot/linux-install/pxelinux.cfg/C0A8010C
    

Expected Results:  The file
/tftpboot/linux-install/pxelinux.cfg/C0A8010C should have made some
mention of the location of the kickstart file (ks.cfg in above example).


Additional info:

It is not clear what you would have to enter for the location of the
kickstart file if you wanted it to be pulled from an NFS server.

Comment 1 Daniel Walsh 2003-11-21 19:07:55 UTC
Grab the latest one out of Rawhide, which has this fixed.
redhat-config-netboot-0.1.2-2.src.rpm

Dan


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