Bug 64287

Summary: Issues with Kickstart and ks.cfg via http
Product: [Retired] Red Hat Linux Reporter: Need Real Name <alfw>
Component: anacondaAssignee: Tammy Fox <tammy.c.fox>
Status: CLOSED RAWHIDE QA Contact: Brock Organ <borgan>
Severity: medium Docs Contact:
Priority: medium    
Version: 7.2   
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2002-07-17 21:27:45 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 67218    

Description Need Real Name 2002-05-01 17:44:06 UTC
From Bugzilla Helper:
User-Agent: Mozilla/4.78 [en] (X11; U; Linux 2.4.18-0.4 i686)

Description of problem:
There are (at least) three "issues" or bugs when I am starting a Kickstart
installation of RH7.2 where the ks.cfg file should be retrieved via http:
1. The Kickstart documentation
(RHL-7.2-Manual/custom-guide/s1-kickstart2-startinginstall.html)
gives a wrong syntax. It should be: ks=http://<server>[:port]/<path>
2. anaconda's loader.c has a mini bug in line 2112. It is
  logMessage("ks location: http:/%s/%s", ksPath, file);
and should be:
  logMessage("ks location: http://%s/%s", ksPath, file);
3. anaconda's urls.c has an "issue" at the beginning of method
urlinstStartTransfer(). When I am using the URL http://server.example.com/ks.cfg
it actually looks for a file "/./ks.cfg" which is sort of ugly.

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


How reproducible:
Always

Steps to Reproduce:
1. Create a boot floppy with dd if=bootnet.img of=/dev/fd0
2. Modify the created syslinux.cfg file on that floppy to use Kickstart by
(e.g.) changing the "text" install section to:
label text
  kernel vmlinuz
  append ks=http:server.example.com:/ks.cfg initrd=initrd.img network
This is the wrong syntax from your documentation.
3. Boot a machine with that floppy.
4. Select "text installation" to trigger the Kickstart installation
5. After a while switch to virtual screen 3 to see the log messages
	

Actual Results:  The machine will not even try to download the ks.cfg from a web
server. If you change the syntax of a:\syslinux.cfg from the one typed
in step 2. above to
  append ks=http://server.example.com/ks.cfg initrd=initrd.img network
and repeat the process from above you will see that this syntax makes
the machine actually try to download the ks.cfg file.

Expected Results:  I expect the machine to download the ks.cfg from my web
server and
continue with its installation.

Additional info:

Comment 1 Michael Fulbright 2002-05-02 15:24:28 UTC
Thank you for the report, we'll get these corrected.

Comment 2 Michael Fulbright 2002-07-17 18:47:17 UTC
I addressed most the technical issues in this report.

I've forwards the documentation issue to docs.


Comment 3 Tammy Fox 2002-07-17 21:59:30 UTC
The docs have been fixed for the http syntax.

Comment 4 Michael Fulbright 2002-12-20 17:38:25 UTC
Time tracking values updated