This is possibly a firmware issue, seeing as the default state for grub
as provided by maas/curtin config should be to skip modifying nvram.
However, how is the system booting in general? Was BootOrder really set
to booting to the network first? If it's set to other devices, and the
other device happens to be the hard disk, then shim fallback may cause a
new variable to be written to nvram to boot to 'ubuntu', and that
variable will always be written as a new thing to boot to first.
** Changed in: grub2 (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1750732
Title:
grub package will change the boot order for MaaS deployed system
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/curtin/+bug/1750732/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
