Comment 58 for bug 1789650

On Tue, Aug 4, 2020 at 8:50 PM Greg McNutt <email address hidden>
wrote:

> Not sure about where or how far to push ubuntu down the list, especially
> when a system has 2 or more potential bootable network devices.
>
> I have run into the same thing with MaaS setup.
> - 2.8.1 MaaS
> - Supermicro in UEFI mode
> - two networks connected (in a LAG)
>
> The problem is that after a deploy, the first network is brought ahead
> of 'ubuntu' so the boot order is UEFI0,ubuntu,UEFI1,UEFI2,UEFI3
>
> And since MaaS can set either 0 or 1 to be PXE boot, on the systems
> where network 1 is set for PXE then no chance to boot from network --
> the local storage is ahead.
>
> Perhaps our workaround is to suppress the ubuntu(disk) entry completely?
>

I think the most robust solution is to somehow confirm which entry MAAS
uses to PXE boot, and supply this entry (BootNumber and the path) to
curtin; then we can ensure that the same entry is first, and the target
distro
entry is second.

That's going to require a bit more work on the MAAS side.

In the meantime, we'll do a reasonable effort to try to make systems lacking
a BootCurrent entry to be bootable for MAAS.

> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1789650
>
> Title:
> Servers set to boot from disk after MAAS installation
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/curtin/+bug/1789650/+subscriptions
>