I'm seeing this with a HP NC523SFP 10G NIC and MASS 2.4.0~beta2 on Ubuntu 18.04. If I UEFI boot from the NIC, it eventually brings up a grub shell. Taking a packet capture confirmed the same ARM storm behaviour when attempting to boot - thousands of packets from the server that is being commissioned requesting the MAC of the MAAS server. Running net_bootp from the grub prompt results in the "error: couldn't send network packet." error, and running net_nslookup for a domain results in an endless ARP storm!
Unfortunately, the last firmware release for this NIC was a few years ago and i'm already running the latest version. Reading the comments here, it sounds like my only hope is a fix within grub2 - however that should already be live. The version of grub booted is grub2 2.02~beta2-36ubuntu3.18, which according to the comments here should fix it.
I'm seeing this with a HP NC523SFP 10G NIC and MASS 2.4.0~beta2 on Ubuntu 18.04. If I UEFI boot from the NIC, it eventually brings up a grub shell. Taking a packet capture confirmed the same ARM storm behaviour when attempting to boot - thousands of packets from the server that is being commissioned requesting the MAC of the MAAS server. Running net_bootp from the grub prompt results in the "error: couldn't send network packet." error, and running net_nslookup for a domain results in an endless ARP storm!
Unfortunately, the last firmware release for this NIC was a few years ago and i'm already running the latest version. Reading the comments here, it sounds like my only hope is a fix within grub2 - however that should already be live. The version of grub booted is grub2 2.02~beta2- 36ubuntu3. 18, which according to the comments here should fix it.
I've also tried using the 2.02-2ubuntu8 version of bootx64.efi, by grabbing it from http:// archive. ubuntu. com/ubuntu/ dists/bionic/ main/uefi/ grub2-amd64/ 2.02-2ubuntu8/ grubnetx64. efi.signed and replacing /var/lib/ maas/boot- resources/ current/ bootloader/ uefi/amd64/ grubx64. efi but with the same result.