Bug 184485 - Anaconda command line truncated
Summary: Anaconda command line truncated
Status: CLOSED NEXTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 4
Classification: Red Hat
Component: pxe
Version: 4.0
Hardware: i686
OS: Linux
medium
medium
Target Milestone: ---
: ---
Assignee: Daniel Walsh
QA Contact: Brock Organ
URL:
Whiteboard:
Keywords:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2006-03-09 07:58 UTC by Loic Domaigne
Modified: 2007-11-30 22:07 UTC (History)
1 user (show)

(edit)
Clone Of:
(edit)
Last Closed: 2006-09-19 17:08:40 UTC


Attachments (Terms of Use)

Description Loic Domaigne 2006-03-09 07:58:05 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.0.1) Gecko/20060111 Firefox/1.5.0.1

Description of problem:
We are installing RHEL AS 4 update 2 using Kickstart over PXE boot. The image that is TFTP'ed and used during the install process is the one found in /images/pxeboot directory on the 1st CD (vmlinuz and initrd.img) 

We're passing the following command line to anaconda in order to perform our installation: 
runks=1 ksdevice=eth0 ks=http://172.24.52.90/bootix/Opodo/mucopXYZT.cfg text

However, the installation failed, and we get the following error message:
* ks location: http://172.24.52.90/bootix/Opodo/mucopX
* transferring http://172.24.52.90//./bootix/Opodo/mucopX to a fd 
* failed to retrieve http://172.24.52.90///bootix/Opodo/mucopX

It seems that the command line got truncated after the 64th characters. 

If I change the command line so that it fits to 64 characters, then the installation works as expected.


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


How reproducible:
Always

Steps to Reproduce:
1. setup environment to install the OS over PXE using kickstart 
2. pass a command line that is greater than 64 bytes 
3.
  

Actual Results:  The command line gets truncated. As a result, the kickstart filename is wrong, and hence the file cannot be found. The installation process stops. 

Expected Results:  kickstart file should have been downloaded and the OS installed. 

Additional info:

Note that we didn't had this issue using RHEL AS 3.


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