Comment I made on https://bugs.launchpad.net/maas/+bug/1642298. Was requested to direct it here.
I think this is more of a GRUB issue overall instead of a MAAS issue directly. True it affects MAAS and we can do the debconf selections to work around this issue but overall for quality of Ubuntu I do not believe this is the proper fix. I will give an example without MAAS. 1. First the user installs Ubuntu on a partition on their local disk, EFI is updated so Ubuntu can boot. 2. Second the user installs Windows on another partition. EFI is updates so Windows can boot and its first. 3. User reboots into Ubuntu, runs apt-get, and grub updates changing the boot order so now that Ubuntu boots first. 4. User reboots their machine and Ubuntu boots but the user expected Windows to boot. Overall this is a bad experience to the user. I think the grub code should be smart about this: First check if the grub.efi loader already exists in efibootmgr. If it does not exists add it to the loader and set it to boot first. If it does exist record its current place in the boot order, update the loader and reset the boot order to its previous location. That change would fix this for any user that uses Ubuntu as well as MAAS users. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1714090 Title: grub2 upgrade doesn't preserve current boot order. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1714090/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
