Bug 83149

Summary: kickstart ignores dhcp directives about ks.cfg location
Product: [Retired] Red Hat Linux Reporter: Chris Ricker <chris.ricker>
Component: anacondaAssignee: Jeremy Katz <katzj>
Status: CLOSED DUPLICATE QA Contact: Mike McLean <mikem>
Severity: medium Docs Contact:
Priority: medium    
Version: 9   
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2006-02-21 18:51:30 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:

Description Chris Ricker 2003-01-30 19:20:10 UTC 
I've got a dhcp server which serves out kickstart file location:

<partial dhcpd.conf>
 elsif substring (option vendor-class-identifier , 0, 10 ) = "PXEClient:" {
      next-server 10.100.0.254 ;
      filename "eepro100.pxe" ;
} elsif substring (option vendor-class-identifier , 0, 4 ) = "MSFT" {
} else {
    filename "/exports/kickstart/workstations-8.1.ks";
    next-server 10.100.0.254;
}

Since anaconda doesn't send an interesting VCI, it just gets the:

    filename "/exports/kickstart/workstations-8.1.ks";
    next-server 10.100.0.254;

If I boot beta4 off of cd and give it

linux ks

at the stage1 loader prompt, it fails to retrieve a kickstart file and goes
straight into the interactive CD-based install

I have to boot it with

linux ks=nfs:blah,blah,blah

to get it to find the kickstart file over the net and use it
Comment 1 Michael Fulbright 2003-01-30 19:53:05 UTC 
I'll take a look.
Comment 2 Jeremy Katz 2003-01-30 19:55:55 UTC 

*** This bug has been marked as a duplicate of 82404 ***
Comment 3 Red Hat Bugzilla 2006-02-21 18:51:30 UTC 
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.