[2.6a1] MAAS provides bogus log messages when a 'device' tries to PXE boot

[Mark Shuttleworth]

I am testing a new workstation board with MAAS and am unable to PXE boot. The rackd shows this in the logs:

... prov...s.tftp: [info] bootx64.efi requested by 192.168.1.39
... prov...s.tftp: [info] bootx64.efi requested by 192.168.1.39
... prov...s.tftp: [info] grubx64.efi requested by 192.168.1.39
... prov...s.tftp: [info] /grub/x86_64-efi/command.lst requested by 192.168.1.39
... prov...s.tftp: [info] /grub/x86_64-efi/fs.lst requested by 192.168.1.39
... prov...s.tftp: [info] /grub/x86_64-efi/crypto.lst requested by 192.168.1.39
... prov...s.tftp: [info] /grub/x86_64-efi/terminal.lst requested by 192.168.1.39
... prov...s.tftp: [info] /grub/grub.cfg requested by 192.168.1.39
... prov...s.tftp: [info] /grub/grub.cfg-70:85:c2:a6:9e:f7 requested by 192.168.1.39
... prov...s.tftp: [info] ubuntu///bionic/no-such-image/boot-kernel requested by 192.168.1.39

[Andres Rodriguez (andreserl)]

As per discussion over IRC, the reason why this machine was failing to PXE boot is because there was a device already added with the same MAC address.

That said, MAAS should deal with the failure a bit more gracefully in that:

 - If a system that is added as a device is trying to PXE boot, MAAS should log a correct warning noting the user that devices are not PXE bootable by MAAS. This should be instead of providing an error that implies images do not exist (ubuntu///bionic/no-such-image/boot-kernel).

 - We should completely ignore PXE boot requests from MAC addresses added as devices.

I'm re-targeting this bug report.

[Mark Shuttleworth (sabdfl)]

Could we make sure there is an entry in the relevant logs, as well as an
entry in the history of events on the device, reflecting this?

Mark