[et-mgmt-tools] cobbler kickstart does not pull in the http: ks file?

Terry McIntyre terry.mcintyre at gmail.com
Fri Apr 4 22:59:46 UTC 2008


On Fri, Apr 4, 2008 at 10:22 AM, Ben Riggs <rigg0022 at umn.edu> wrote:
> To be sure that anaconda is using the card you want it to (I've noticed
> inconsistencies between the eth#s in bios, anaconda & 'normal' kernels), add
> --kopts="device=$nic_mac_address"

Ok, I used --kopts="device=", and it is reflected in the
/var/lib/cobbler/systems file:

    depth: 2
    interfaces:
        intf0:
            dhcp_tag: ''
            gateway: '192.168.62.40'
            hostname: rac12
            ip_address: '192.168.62.172'
            mac_address: '00:15:17:3a:c2:78'
            subnet: ''
            virt_bridge: ''
        intf1:
            dhcp_tag: ''
            gateway: ''
            hostname: ''
            ip_address: '192.168.62.173'
            mac_address: '00:14:5e:bc:69:e2'
            subnet: ''
            virt_bridge: ''
    kernel_options:
        device: '00:15:17:3a:c2:78'
    kickstart: <<inherit>>
    ks_meta:
        hostname: rac12.crm.bizsys.tmcs
        ip: '192.168.62.172'
    name: '00:15:17:3a:c2:78'
    netboot_enabled: True

Here's tail -f /var/log/messages:

Apr  4 15:39:22 admin dhcpd: dhcpd startup succeeded
Apr  4 15:39:22 admin dhcpd: dhcpd startup succeeded
Apr  4 15:42:52 admin dhcpd: DHCPDISCOVER from 00:15:17:3a:c2:78 via eth0
Apr  4 15:42:52 admin dhcpd: DHCPOFFER on 192.168.62.172 to
00:15:17:3a:c2:78 via eth0
Apr  4 15:42:54 admin dhcpd: DHCPREQUEST for 192.168.62.172
(192.168.63.57) from 00:15:17:3a:c2:78 via eth0
Apr  4 15:42:54 admin dhcpd: DHCPACK on 192.168.62.172 to
00:15:17:3a:c2:78 via eth0
Apr  4 22:42:54 admin in.tftpd[19942]: RRQ from 192.168.62.172
filename /pxelinux.0
Apr  4 22:42:54 admin in.tftpd[19942]: tftp: client does not accept options
Apr  4 22:42:54 admin in.tftpd[19943]: RRQ from 192.168.62.172
filename /pxelinux.0
Apr  4 22:42:56 admin in.tftpd[19944]: RRQ from 192.168.62.172
filename /pxelinux.cfg/01-00-15-17-3a-c2-78
Apr  4 22:42:56 admin in.tftpd[19945]: RRQ from 192.168.62.172
filename //images/rhel4.4/vmlinuz
Apr  4 22:42:57 admin in.tftpd[19946]: RRQ from 192.168.62.172
filename //images/rhel4.4/initrd.img

At this point it is booting, I see an anaconda version, and /sbin/loader
next thing is a screen requesting IP address via dhcp.

Apr  4 15:43:23 admin dhcpd: DHCPDISCOVER from 00:15:17:3a:c2:78 via eth0
Apr  4 15:43:23 admin dhcpd: DHCPOFFER on 192.168.62.172 to
00:15:17:3a:c2:78 via eth0
Apr  4 15:43:29 admin dhcpd: DHCPDISCOVER from 00:15:17:3a:c2:78 via eth0
Apr  4 15:43:29 admin dhcpd: DHCPOFFER on 192.168.62.172 to
00:15:17:3a:c2:78 via eth0
Apr  4 15:43:40 admin dhcpd: DHCPDISCOVER from 00:15:17:3a:c2:78 via eth0
Apr  4 15:43:40 admin dhcpd: DHCPOFFER on 192.168.62.172 to
00:15:17:3a:c2:78 via eth0
Apr  4 15:43:50 admin dhcpd: DHCPDISCOVER from 00:15:17:3a:c2:78 via eth0
Apr  4 15:43:50 admin dhcpd: DHCPOFFER on 192.168.62.172 to
00:15:17:3a:c2:78 via eth0
Apr  4 15:43:50 admin dhcpd: DHCPDISCOVER from 00:15:17:3a:c2:78 via eth0
Apr  4 15:43:50 admin dhcpd: DHCPOFFER on 192.168.62.172 to
00:15:17:3a:c2:78 via eth0

Why is it looping?

After this loop, Anaconda then shows the "Use dynamic IP configuration" screen.

The kickstart file ( referenced here ) is not being requested, so far
as I can tell:

[root at admin pxelinux.cfg]# cat /tftpboot/pxelinux.cfg/01-00-15-17-3a-c2-78
default linux
prompt 0
timeout 1
label linux
        kernel /images/rhel4.4/vmlinuz
        append ksdevice=eth0 lang=en_US text
syslog=192.168.63.57:25150 device=00:15:17:3a:c2:78 kssendmac
initrd=/images/rhel4.4/initrd.img
ks=http://192.168.63.57/cblr/kickstarts_sys/00:15:17:3a:c2:78/ks.cfg

Oddly, there is no newline on the last line of this file.

I cut-n-pasted this url
http://192.168.63.57/cblr/kickstarts_sys/00:15:17:3a:c2:78/ks.cfg into
a browser on my laptop on the same network, and it worked properly.

/etc/httpd/logs/access_log shows my request ( by hand ); it shows no
previous request from anaconda.

I added a linefeed to the end of the pxelinux.cfg file and tried
again. No change in behavior.




More information about the et-mgmt-tools mailing list