This service will be undergoing maintenance at 00:00 UTC, 2017-10-23 It is expected to last about 30 minutes
Bug 83149 - kickstart ignores dhcp directives about ks.cfg location
kickstart ignores dhcp directives about ks.cfg location
Status: CLOSED DUPLICATE of bug 82404
Product: Red Hat Linux
Classification: Retired
Component: anaconda (Show other bugs)
9
All Linux
medium Severity medium
: ---
: ---
Assigned To: Jeremy Katz
Mike McLean
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2003-01-30 14:20 EST by Chris Ricker
Modified: 2008-01-17 12:49 EST (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2006-02-21 13:51:30 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 Chris Ricker 2003-01-30 14:20:10 EST
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 14:53:05 EST
I'll take a look.
Comment 2 Jeremy Katz 2003-01-30 14:55:55 EST

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

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