>From this point I don't think this is a dup as I can see the "ubuntu" entry for both of the AMD Naples amd64 server and the TunderX arm64 server, with Bionic:
efibootmgr output after they have been deployed: ubuntu@wright-kernel:~$ sudo efibootmgr BootCurrent: 0002 Timeout: 10 seconds BootOrder: 0002,0003,0004,0000,0001 Boot0000* ubuntu Boot0001 UEFI: Built-in EFI Shell Boot0002* UEFI: IP4 Ethernet vNIC Controller 62:54:CA Boot0003* UEFI: IP4 Ethernet vNIC Controller 62:54:CB Boot0004* UEFI: IP4 Ethernet vNIC Controller 62:54:CC ubuntu@lodygin:~$ sudo efibootmgr BootCurrent: 0002 Timeout: 1 seconds BootOrder: 0002,0000,0003,0004 Boot0000* ubuntu Boot0002* UEFI: IP4 Intel(R) Gigabit CT Desktop Adapter Boot0003* UEFI: Built-in EFI Shell Boot0004* Hard Drive The only difference is that the grub package from proposed will change the boot order only on the AMD server: ubuntu@lodygin:~$ sudo efibootmgr BootCurrent: 0002 Timeout: 1 seconds BootOrder: 0000,0002,0003,0004 Boot0000* ubuntu Boot0002* UEFI: IP4 Intel(R) Gigabit CT Desktop Adapter Boot0003* UEFI: Built-in EFI Shell Boot0004* Hard Drive -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1790586 Title: The proposed grub package in Trusty / Bionic overrides the boot order on a MaaS deployed system To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1790586/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
