For that, first I had to upgrade current curtin (on each infra node):
sudo add-apt-repository ppa:curtin-dev/stable
sudo apt update
sudo apt install --only-upgrade curtin-common
Then I had to add the fallback option to the /etc/maas/preseeds/curtin_userdata
reorder_uefi_force_fallback: True
Hi, I am seeing the same issue on MAAS + HPE Synergy Gen 10.
I can see Michal found a solution for his issue. I will leave what I've tested for the discussion.
It sets BIOS as the second viable option by the end of curtin. /git.launchpad. net/curtin/ tree/curtin/ commands/ curthooks. py?h=ubuntu/ bionic& id=a1d98115e5dc 2b525a3f7556f4f 97dd48693f608
Looking at the code we generally run with Bionic version, I can see there is not much logic on it to customize boot order:
https:/
However, on newer 20.2, there is an extra option: https:/ /github. com/canonical/ curtin/ blob/81144052c6 4a3d22edb68ebbd 11483b463e62656 /curtin/ commands/ curthooks. py#L520 uefi_force_ fallback
reorder_
In my case, after setting that, I can see the boot order got rearranged on curtin logs: /pastebin. canonical. com/p/mMp7BvbRW G/ /pastebin. canonical. com/p/FCCQtxQH2 9/
Before: https:/
After: https:/
For that, first I had to upgrade current curtin (on each infra node): dev/stable
sudo add-apt-repository ppa:curtin-
sudo apt update
sudo apt install --only-upgrade curtin-common
Then I had to add the fallback option to the /etc/maas/ preseeds/ curtin_ userdata uefi_force_ fallback: True
reorder_
According to the docs: https:/ /curtin. readthedocs. io/en/latest/ topics/ config. html
I believe we should leave this option as True on preseed.