TFTP documentation

Users
1

Hi
Would it be possible to document how maas 3.6 tftpd deamon works within rackd?

I am facing an issue where the tftp rootfolder is /var/snap/maas/common/maas/tftp_root (i found this by doing “find / | grep tftp”)

but the actual required files(testing with uefi boot) are stored in
/var/snap/maas/common/maas/image-storage/bootloaders/uefi/amd64

Copying them to the /var/snap/maas/common/maas/tftp_root “solves” the problem.

but i have a strong feeling this is not the intended way,
The documentaion; Networking is to generic about the tftp protocol and not enough about the settings.
ChatGPT is worthless when it comes to maas - it references old versions all the time, it’s a complete waste of time.

2

What files did you copy there? There should be no need for it, because MAAS is supposed to pick the files from /var/snap/maas/common/maas/image-storage/bootloaders/uefi/amd64 when the machines are requesting them

3

exactly what i expected,
How do i debug that process? (the magic part that selects and copy the right file to the right dir)

I copied bootx64.efi and grubx64.efi

4

AFAIK this is not needed at all. There is no such magic anywhere. Probably your MAAS was still downloading the images. Can you try to remove them from that tftp_root, ensure that all the images are in sync from the MAAS UI and retry?

5

i want to deploy a custom image, it deploys “fine” on a VM running on Nutanix. but i am testing it on a laptop now.

Is there no debug flag’s that can be set?

6

you can edit /var/snap/maas/current/rackd.conf and add debug: True.

7

@mortenkallesoe6734 , did you get this one resolved? can i close it?

8

Hi Billwear - yes, i have not tried out the debug option though.
After fiddling around with some other problems, we saw that the ip was assigned to multiple hosts, so this is properly the case why the “magic” the in the tftp part of rackd was not working properly.