On 07/28/2009 10:44 AM, James Cammarata wrote:
On Tue, 28 Jul 2009 10:03:44 -0400, "Brown, Scott D CTR, E2"
<scott.brown4.ctr@navy.mil> wrote:
  
Good morning.  I have a question reguarding Kickstarts.  I have a custom
kickstart file I've been using in the early days of Cobbler and wish to
use them in the current version of Cobbler.

After copying the DVD ISO image to the computer and mounting it, I did a
cobbler import --path=<path to the image> --name=RHEL53_x64
--kickstart=<path to the ks.cfg file> --breed=redhat.  All indications
seem to be fine after importing until I tried to boot off my VM
Workstation to test out the configuration.

I can get to cobblers DHCP and the boot menu, but when I select the
profile, the kickstart never fires off.  After selecting the profile all
    
I
  
get is the normal installation window for RedHat where as from the
kickstart file attached it should do an unattended install.  As part of
    
my
  
troubleshooting I did a cobbler profile report and it shows the kickstart
path to the ks.cfg.  Any help would be appreciated.  Thanks.. 

V/R
Scott Brown
NAVAIR PMA-231 SysAdmin
CompTIA Security+
CompTIA Linux+
    

Make sure cobbler is copying the initrd/kernel to /tftpboot/images/<distro
name>/.  You also may want to add a -vvv to your tftpd configuration
(/etc/xinetd.d/tftp, on the server_args line) to increase logging verbosity
and tail /var/log/messages after you select the profile to see if tftpd is
running into an error (permissions, selinux, etc.).


  


Also, (this should be to the main list, so replies to there, if you don't mind) ...

A few thoughts:

(A) Run "cobbler check" to see if anything is mentioned that you need to fix

(B)  Also do "cobbler profile getks --name=foo" to verify there is a kickstart file is set up as you would expect.

(C)  Make sure you are not installing off of a second cobbler server if you have more than one.  It would depend on what DHCP was pointing you at.

(D)  Finally check http://cobbler.example.org/cblr/svc/op/ks/profile/namegoeshere to see if that URL is accessible from your installation network.

Hope that helps,

--Michael