FWIW, I did a bit of extra testing. I killed maas' rackd (which provides PXE). Rebooted the machine and I saw:
1. It attempted to PXE boot multiple times (like a lot) 2. It eventually gave up and booted from disk So it successfully booted into the deployed OS. I noticed that the curtin installation reported the boot order, and seems that (1) above was caused because of the following: BootCurrent: 0006 Timeout: 1 seconds BootOrder: 0006,0000,0004,0003,0008,0007,0005,0009,000A Boot0000* ubuntu Boot0003* UEFI: Intel(R) I350 Gigabit Network Connection Boot0004* UEFI: IP4 Intel(R) I350 Gigabit Network Connection Boot0005* UEFI: Intel(R) I350 Gigabit Network Connection Boot0006* UEFI: IP4 Intel(R) I350 Gigabit Network Connection Boot0007* UEFI: Intel(R) 82599 10 Gigabit Dual Port Network Connection Boot0008* UEFI: IP4 Intel(R) 82599 10 Gigabit Dual Port Network Connection Boot0009* UEFI: Intel(R) 82599 10 Gigabit Dual Port Network Connection Boot000A* UEFI: IP4 Intel(R) 82599 10 Gigabit Dual Port Network Connection -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1711203 Title: Deployments fail when Secure Boot enabled To manage notifications about this bug go to: https://bugs.launchpad.net/curtin/+bug/1711203/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
