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

Bug #1820984 reported by Mark Shuttleworth on 2019-03-20
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
MAAS
Medium
Unassigned

Bug Description

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) wrote :

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.

summary: - [2.6a1] PXE fails on new vPro workstation
+ [2.6a1] MAAS provides bogus log messages when a 'device' tries to PXE
+ boot
Changed in maas:
milestone: none → 2.6.0
importance: Undecided → Medium
status: New → Triaged

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

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers