Multiple NICs, partial success, partial weirdness

[Carsten Aulbert]

Once again from the "correct" email address:

Thomas Lange schrieb:
>>>>>> On Tue, 03 Mar 2009 10:49:29 +0100, Carsten Aulbert <carsten at welcomes-you.com> said:
> 
>     >> Yesterday I reinstalled a computer several times, tuning ssh settings
>     >> and other customizations, however, I'm not aware to change something
>     >> substantial, but suddenly it seems the wrong entry in pxeboot.cfg is
>     >> modified:
>     >> 
>     >> grep 'disable' install-200903*/fai.log
>     >> install-20090302_191531/fai.log:disable pxe config for 10.20.30.3 in hex
>     >> 0A141E03
>     >> install-20090302_192700/fai.log:disable pxe config for 172.28.20.3 in
>     >> hex AC1C1403
>     >> install-20090302_193420/fai.log:disable pxe config for 172.28.20.3 in
>     >> hex AC1C1403
>     >> install-20090302_194559/fai.log:disable pxe config for 172.28.20.3 in
>     >> hex AC1C1403
>     >> 
> This is how the task chboot determines the ip address.
> 
> ipaddr=$(grep IPADDR $LOGDIR/boot.log | cut -d\' -f2)
> 
> try: grep 'IPADDR' install-200903*/boot.log
> maybe you'll see where the error comes from.

$ grep 'IPADDR' install-200903*/boot.log
install-20090302_191531/boot.log:IPADDR='10.20.30.3'
install-20090302_192700/boot.log:IPADDR='172.28.20.3'
install-20090302_193420/boot.log:IPADDR='172.28.20.3'
install-20090302_194559/boot.log:IPADDR='172.28.20.3'
install-20090303_094231/boot.log:IPADDR='10.20.30.3'
install-20090303_095307/boot.log:IPADDR='172.28.20.3'
install-20090303_095806/boot.log:IPADDR='10.20.30.3'
install-20090303_103633/boot.log:IPADDR='10.20.30.3'

Thomas, could there be a race condition when multiple DHCP servers are
available and one replies faster then the other?

I'm wondering because */dhclient.log only ever shows one reply but never
both....

Cheers

Carsten