[prev in list] [next in list] [prev in thread] [next in thread] 

List:       linux-fai
Subject:    Minor problem with task_chboot
From:       Andreas Jobs <andreas.jobs () ruhr-uni-bochum ! de>
Date:       2006-03-15 8:47:13
Message-ID: 20060315084713.GA32093 () ruhr-uni-bochum ! de
[Download RAW message or body]


Hi all,

Problem:
task_chboot does not disable the correct pxe configuration.

Description:
If you have more than one NIC, your hostname may not map to the adress
used during install. In my case (installing some Compaq Blade Servers)
the Installation uses eth0 but the "production" interface is eth2. So,
hostname resolves to the address bind to eth2. During task_chboot fai
does "fai_chboot -r $hostname" and quits with a file not found message.

Solution:
Use the address that was used during installation. My quick-and-dirty
patch currently is:

--- subroutines-linux.orig      2006-01-12 17:49:49.000000000 +0100
+++ subroutines-linux   2006-03-10 09:41:23.000000000 +0100
@@ -185,7 +185,8 @@

     local frsh
     local doexit=0
-    local hostname=$(hostname)
+    local hostname=$(cat $LOGDIR/boot.log | grep IPADDR | cut -d\' -f2)
+    [ -z "$hostname" ] && hostname=$(hostname)
     frsh="$FAI_REMOTESH -l $LOGUSER ${SERVER}"


Maybe there is a better (cleaner) solution.

I'd like to file a bug in BTS. Should I file it to "fai" or
"fai-client"?

Andreas

-- 
! Andreas Jobs                                 Network Operating Center !
!                                              Ruhr-Universitaet Bochum !
! The only way to clean a compromised system is to flatten and rebuild. !

[Attachment #3 (application/pgp-signature)]

[prev in list] [next in list] [prev in thread] [next in thread]