With my suggested change to ignore BootCurrent since it does not have a matching entry; curtin can at best put the new entry 0000 first in order (note this is already done by grub-install).
This does mean that the node will be lost from maas control since it is no longer PXE booting...
Is that acceptable?
@Dann
For this firmware bug where we have missing entries; Have you ever booted this up and had efibootmgr show all of the entries?
Looking at this output here:
BootCurrent: 0003 0004,0005, 0006,0001 0937ffdf- 628c-4161- 8b2f-5920235669 c6,0x800, 0x100000) /File(\ EFI\ubuntu\ shimx64. efi)
Timeout: 10 seconds
BootOrder: 0000,0003,
Boot0000* ubuntu HD(1,GPT,
With my suggested change to ignore BootCurrent since it does not have a matching entry; curtin can at best put the new entry 0000 first in order (note this is already done by grub-install).
This does mean that the node will be lost from maas control since it is no longer PXE booting...
Is that acceptable?