Question

1

Enlisted MAAS nodes will not PXE boot for commissioning

rated 0 times [ 1] [ 0] / answers: 1 / hits: 10679 / 2 Years ago, mon, january 17, 2022, 4:01:05

I'm wondering if any of you can assist with the issues I'm facing with MAAS. I have a working MAAS server that is running DNS and DHCP. I built the MAAS server on 13.04 server. I couldn't get any of the nodes to enlist (show up on the home page of MAAS) with the 13.04 server disc. When I used 12.04, they were enlisted.

However, now that they are enlisted, I cannot get them to commission. They will receive a DHCP response and IP address from the MAAS server and then they will try to boot to an image called pxelinux.cfg/XX-XX-XX-XX-XX-XX-XX where the X's are a MAC address. It just hangs there. I have attached a screenshot. Can anyone assist?

Answers

Only authorized users can answer the question. Please sign in first, or register a free account.

amencisiv

Add To Favorites

Follow

Total Points: 9

Total Questions: 102

Total Answers: 118

Location: Tajikistan

Member since Tue, Mar 21, 2023

1 Year ago

amencisiv questions

1 Could not install any app via Software in Ubuntu 22.04

Wed, Dec 28, 22, 12:58, 1 Year ago

1 Firefox occasionally not rendering its own window when opened

Sat, Jan 28, 23, 09:23, 1 Year ago

1 Apache restart only for one web page Ubuntu 20.04

Wed, Sep 28, 22, 18:24, 2 Years ago

1 IdeaPad 5 15are05 - elan touchpad not working on 20.04 nor on 18.04

Sun, May 7, 23, 11:26, 1 Year ago

1 Is snap verified by Ubuntu SnapCraft Team?

Fri, May 13, 22, 19:08, 2 Years ago

View All

answered 2 Years ago cheeturage · Accepted Answer

After analyzing /var/log/maas/pserv.log, which is the PXE/TFTP boot server log, I noticed that it was complaining that there were no PXE images, or ephemerals, found on the server. The log asked to run maas-import-pxe-files again, even though I had run it multiple times.

2013-05-06 08:02:40-0400 [HTTPPageGetter,client] Stopping factory <HTTPClientFactory: http://localhost/MAAS/api/1.0/pxeconfig/?cluster_uuid=91149761-d1

49-4396-86a0-a3a2a6b57c7d&local=192.168.60.10&mac=08-00-27-3c-7b-91&remote=192.168.60.106>

2013-05-06 08:02:40-0400 [HTTPPageGetter,client] Stopping factory <HTTPClientFactory: http://localhost/MAAS/api/1.0/pxeconfig/?cluster_uuid=91149761-d1

49-4396-86a0-a3a2a6b57c7d&local=192.168.60.10&mac=08-00-27-3c-7b-91&remote=192.168.60.106>

2013-05-06 08:02:40-0400 [HTTPPageGetter,client] Logged OOPS id OOPS-bdc099b3ed2983f2eb94d6096a811915: No exception type: No exception value

2013-05-06 08:02:40-0400 [HTTPPageGetter,client] Logged OOPS id OOPS-ac4bdf5b247f85d2cb53baf0aa4c2183: EphemeralImagesDirectoryNotFound: The directory 

containing the ephemeral images/info is missing (u'/var/lib/maas/ephemeral/raring/ephemeral/amd64').  Make sure to run the script 'maas-import-pxe-file

s'.

Notice, that it's looking in a raring directory for ephemerals. This directory doesn't exist.

After running the command again, I noticed that the maas-import-pxe-files only downloads ephemerals for Precise and Quantal, not Raring.

irossi@maasjuju:~$ maas-import-pxe-files 

This utility may only be run as root.

irossi@maasjuju:~$ sudo !!

sudo maas-import-pxe-files 

Downloading to temporary location /tmp/tmp.uTLWpre2Uz.

/tmp/tmp.uTLWpre2Uz ~

2013-05-06 08:14:25 URL:http://archive.ubuntu.com/ubuntu//dists/precise/main/installer-amd64/current/images/netboot/ubuntu-installer/amd64//linux [4965840/4965840] -> "linux" [1]

2013-05-06 08:17:04 URL:http://archive.ubuntu.com/ubuntu//dists/precise/main/installer-amd64/current/images/netboot/ubuntu-installer/amd64//initrd.gz [17446386/17446386] -> "initrd.gz" [1]

2013-05-06 08:17:18 URL:http://archive.ubuntu.com/ubuntu//dists/quantal/main/installer-amd64/current/images/netboot/ubuntu-installer/amd64//linux [5130968/5130968] -> "linux" [1]

2013-05-06 08:18:28 URL:http://archive.ubuntu.com/ubuntu//dists/quantal/main/installer-amd64/current/images/netboot/ubuntu-installer/amd64//initrd.gz [18668122/18668122] -> "initrd.gz" [1]

2013-05-06 08:18:45 URL:http://archive.ubuntu.com/ubuntu//dists/precise/main/installer-i386/current/images/netboot/ubuntu-installer/i386//linux [5015840/5015840] -> "linux" [1]

2013-05-06 08:19:35 URL:http://archive.ubuntu.com/ubuntu//dists/precise/main/installer-i386/current/images/netboot/ubuntu-installer/i386//initrd.gz [15977428/15977428] -> "initrd.gz" [1]

2013-05-06 08:20:37 URL:http://archive.ubuntu.com/ubuntu//dists/quantal/main/installer-i386/current/images/netboot/ubuntu-installer/i386//linux [5171760/5171760] -> "linux" [1]

I checked in the MAAS Server settings page (the gray gear icon) and the default distro for nodes was set to Raring Ringtail 13.04. The nodes were looking for a boot image for Raring that wasn't there. As soon as I changed this setting to Precise 12.04 as the default distro, all of the nodes booted successfully and were commissioned. It's working now, but I'm still not sure if this is user error or a bug. If anyone thinks it's a bug, I'll be glad to file it in Launchpad.