I'm wondering if we need to change the kickstart template too, e.g. we have this in the template:

network --device eth0 --bootproto dhcp

maybe we should store the interface name and change this accordingly?

imho its a best practice to boot your servers from eth0, but that's another store :)

Do you want to post the diff as a git patch (so we'll know who to blame later on :))

Ohad Levy wrote:

I'm wondering if we need to change the kickstart template too, e.g. we have this in the template:

[...]

maybe we should store the interface name and change this accordingly?

Playing around with it a bit, I found that at least with a DHCP config, you can just leave out the device argument and anaconda will just Do The Right Thing:

network --bootproto dhcp

However, I did have to modify my syslinux config file to get kickstart. Basically, the ipappend and ksdevice options here tell kickstart to use the same device that the machine PXE booted off of, regardless of interface name:

default linux
label linux
  ipappend 2
  kernel pxelinux.cfg/c5-x86_64-vmlinuz
  append initrd=pxelinux.cfg/c5-x86_64-initrd.img text ip=dhcp lang=en_US keymap=us ks=http://foreman/unattended/kickstart ksdevice=bootif

imho its a best practice to boot your servers from eth0, but that's another store :)

I agree - unfortunately I have some new servers that disagree, and insist on enumerating the add-in 10G NICs before the on-board 1G NICs :P

Do you want to post the diff as a git patch (so we'll know who to blame later on :))

Sure, why not? =)

Frank Sweetser wrote:

Ohad Levy wrote:

I'm wondering if we need to change the kickstart template too, e.g. we have this in the template:

[...]

maybe we should store the interface name and change this accordingly?

Playing around with it a bit, I found that at least with a DHCP config, you can just leave out the device argument and anaconda will just Do The Right Thing:

is that only on RHE5? I'm unsure about older versions of RH.

[...]

However, I did have to modify my syslinux config file to get kickstart. Basically, the ipappend and ksdevice options here tell kickstart to use the same device that the machine PXE booted off of, regardless of interface name:

dont we need to specifiy the ksdevice (to match to the booted interface)?
Its already planned to generate the actual pxelinux config file rather then to link, so we could actually use the same value (maybe set it up in the gui upfront).

[...]

imho its a best practice to boot your servers from eth0, but that's another store :)

I agree - unfortunately I have some new servers that disagree, and insist on enumerating the add-in 10G NICs before the on-board 1G NICs :P

cant you just disable the interfaces in bios? this usually solves the problem (unless you need it later on)

Applied in changeset 924cdd0a7d03c02aa195d8a7137729e0130f32ca.