From srg67 at bath.ac.uk  Mon Feb  3 14:07:07 2025
From: srg67 at bath.ac.uk (Stuart Green)
Date: Mon, 3 Feb 2025 13:07:07 +0000
Subject: New to FAI, having some issues building
In-Reply-To: <CWLP302MB026352740E729C38327432A49EE92@CWLP302MB0263.GBRP302.PROD.OUTLOOK.COM>
References: <CWLP302MB026352FC512C624A3B7D9D749EE02@CWLP302MB0263.GBRP302.PROD.OUTLOOK.COM>
 <mailman.133269.1737645838.126908.linux-fai@uni-koeln.de>
 <26514.25963.795555.636238@cs.uni-koeln.de>
 <mailman.133918.1737650314.126909.linux-fai@uni-koeln.de>
 <26514.29499.907688.957127@cs.uni-koeln.de>
 <mailman.134157.1737659717.126910.linux-fai@uni-koeln.de>
 <26519.18412.211077.396630@cs.uni-koeln.de>
 <CWLP302MB0263EC31CE7B067EAC7700C39EE92@CWLP302MB0263.GBRP302.PROD.OUTLOOK.COM>
 <CWLP302MB026352740E729C38327432A49EE92@CWLP302MB0263.GBRP302.PROD.OUTLOOK.COM>
Message-ID: <CWLP302MB0263DFCAFA38DF319D640C119EF52@CWLP302MB0263.GBRP302.PROD.OUTLOOK.COM>

Hi again..

I've got something concrete now.

I found some discussions around dhcp option 12 and a suggestion that for option 12 to work the client cannot have a static name.

After the build run /etc/hostname was set to localhost - which I thought I read should be ignored, however I rm'd /etc/hostname and rebooted the machine, sure enough the machine name then set correctly from dhcp.

I guess I need to avoid /etc/hostname being populated with localhost?

Not sure what the correct way is to achieve this

Hashing out the line in /srv/fai/config/scripts/DEBIAN/40-misc

#fcopy -Mv /etc/hostname || echo $HOSTNAME > $target/etc/hostname

Works but I assume there's better places to be affecting this.   It also only works after the first reboot, the build run records its logs under localhost.


Thanks,
Stuart


________________________________
From: Stuart Green <srg67 at bath.ac.uk>
Sent: 30 January 2025 14:22
To: fully automatic installation for Linux <linux-fai at uni-koeln.de>
Subject: Re: New to FAI, having some issues building


One thing I have since noticed, the core networks dhcp server is sending  example.com as the dhcp domain and our sub domain is not included in the domain search it provides.  I can see in the fai boot.log of the localhost machine that the domain is example.com and in the boot.log of the machine with the correct dns name is oursubdomain.example.com, not sure if this is a problem, nslookup works fine on machines with the core networks dhcp server sent information.

Best Regards,
Stuart
________________________________
From: Stuart Green <srg67 at bath.ac.uk>
Sent: 30 January 2025 12:49
To: fully automatic installation for Linux <linux-fai at uni-koeln.de>
Subject: Re: New to FAI, having some issues building

Thanks Thomas and Matthew for the pointers.  I've been testing for a few days but I think I'm quite confused though what the workflow should be with autodiscover.

In the guide it says about autodiscover "This lifts the necessity of having to collect every client?s MAC address and configuring the DHCP daemon."

In my environment I have a vlan which is assigned to us. Within a management system I can register dhcp reservations with mac address, create static IP entries, or set an IP as reserved.
I don't have any access to the dhcp servers backend settings.  Usually we register machines as dhcp reservations with mac address.

I was having zero success getting the hostname to set - I tried Matthews trick with fai-chboot - it didn't help me.
As a side note, I'm slightly confused about how the file created by fai-chboot is involved in the autodiscover workflow, I see its interacted with at the end of the autodiscover process where it sets the file .disable

I then decided to configure the dhcp daemon on the fai server, I also added the new host to /etc/hosts and dhcp-edit and after running another build of a VM the hostname became set!

I'm now able to get it consistently building a machine with the hostname set correct in my Proxmox Environment where the FAI server is also hosted, however when I tried to run the same build on baremetal yesterday the hostname was set to locahost each time.

If dhcp is supposed to be setting the hostname is the issue likely to be that the core networks dhcp server is not setup with use-host-decl-names on and because the baremetal server is not sharing a backplane with the fai server(whereas my test vms do) it always gets a broadcast response quicker from the core networks dhcp server?

Best Regards,
Stuart

________________________________
From: linux-fai <linux-fai-bounces at uni-koeln.de> on behalf of Thomas Lange <lange at cs.uni-koeln.de>
Sent: 27 January 2025 08:46
To: fully automatic installation for Linux <linux-fai at uni-koeln.de>
Subject: Re: New to FAI, having some issues building

[You don't often get email from lange at cs.uni-koeln.de. Learn why this is important at https://aka.ms/LearnAboutSenderIdentification ]

CAUTION:  This email came from outside of the University. To keep your account safe, only click on links and open attachments if you know the person who sent the email, or you expected to receive this communication.



>>>>> On Thu, 23 Jan 2025 19:15:14 +0000, Stuart Green via linux-fai <linux-fai at uni-koeln.de> said:

    > How are hostnames controlled/set when using autodiscover?
Usually the hostname is provided by the DHCP server (via the option use-host-decl-names on).
This also work when using the autodiscover ISO.

--
regards Thomas
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.uni-koeln.de/pipermail/linux-fai/attachments/20250203/9a8c5482/attachment.html>

From lange at cs.uni-koeln.de  Mon Feb  3 16:35:30 2025
From: lange at cs.uni-koeln.de (Thomas Lange)
Date: Mon, 3 Feb 2025 16:35:30 +0100
Subject: FAI 6.2.6 releases
Message-ID: <26528.57922.579544.390711@cs.uni-koeln.de>

A new minor release of FAI (6.2.6) is available. It fixes a small bug
in fai-mirror and for trixie sometimes the grup config was not created.

-- 
best regards Thomas