Hi Michael,

thanks for looking into this!

On Thu Sep 01, 2011 at 11:48:35 +0100, Michael Tautschnig wrote:
> [...]
> 
> May I ask you for the following further information?
> 
> - Is it correct that the above code is executed as part of some script in
>   class/? What is the name of that script?

Yes, that's right.  The script is $FAI_CONFIGDIR/class/60-nis with
permissions 755.

> - What exactly do you refer to as "fails" - is it that the resulting classes 
> do
>   not contain "NIS" (and neither do they contain "$YPDOMAIN")?

Exactly.

> - Did you try to add debugging information like echo'ing "my XXYPDOMAIN:
>   XX$YPDOMAIN" (which might in your case result in XX only, if $YPDOMAIN turns
>   out to be empty)?

Not until you suggested it.  Now I tried echo'ing XX$YPDOMAIN, ending up
with "XX" in the resulting classes list.  So $YPDOMAIN obviously remains
unset (or empty?).

Here's the snippet from fai.log:
<...>
/usr/bin/fai-class: File 60-nis found.
Executing /var/lib/fai/config/class/60-nis.
60-nis               OK.
/usr/bin/fai-class: Adding class XX
<...>

> - What is the contents of boot.log on your client?
> 
The boot.log file on the client contains the following lines:

netdevices_all="eth0"
netdevices_up="eth0"
netdevices="eth0"
BROADCAST='192.168.0.255'
DOMAIN='my.network.domain'
DNSSRVS='192.168.0.11 192.168.0.12 192.168.0.13'
DNSSRVS_1='192.168.0.11'
DNSSRVS_2='192.168.0.12'
DNSSRVS_3='192.168.0.13'
HOSTNAME='demo0'
IPADDR='192.168.0.101'
NETWORK='192.168.0.0'
YPSRVR='192.168.0.2'
YPSRVR_1='192.168.0.2'
NTPSRVS='192.168.0.2'
NTPSRVS_1='192.168.0.2'
GATEWAYS='192.168.0.1'
GATEWAYS_1='192.168.0.1'
SERVER='192.168.0.10'
NETMASK='255.255.255.0'

All the above variables are correct, but the variable

YPDOMAIN='my-nis-domain+01'

is missing, although it's supllied by the DHCP server.

Here's the config line from dhcpd.conf:

option nis-domain "my-nis-domain+01";

When I replace the plus sign by a minus sign, so that the NIS domain
name is "my-nis-domain-01", and doing a faireboot on the install
client, then

1) the NIS domain gets properly set during the installation sequence and
2) the boot.log additionally contains the line

YPDOMAIN='my-nis-domain-01'

and the resulting classes do contain "NIS MY_NIS_DOMAIN_01".

Here's the relevant snippet from fai.log for this case:
<...>
/usr/bin/fai-class: File 60-nis found.
Executing /var/lib/fai/config/class/60-nis.
60-nis               OK.
/usr/bin/fai-class: Adding class NIS MY_NIS_DOMAIN_01
<...>

So the script generally works, if YPDOMAIN finds it's way into boot.log.

I'm not absolutely sure about if this bug should be filed against
fai-nfsroot package, but as far as I tried to debug this, I came across
/usr/share/fai/dhclient-fai-script which is provided as script file to
dhlclient (with -sf option) and simply executes 'perl
/usr/lib/fai/dhclient-perl'.  I filed this bug against fai-nfsroot,
because both those files are part of this package.

Regards,
 Michael

Attachment: signature.asc
Description: Digital signature

Reply via email to