@Dann Thanks.
Can you provide the log without your changes? Or at least the
efibootmgr dump before curtin starts processing things?
> Notice we have no entry for current/0003. I have not inspected the code to
> determine whether or not this is an issue parsing efibootmgr output or the
> actual variable state.
Is this not the bug? The full logs will show what efibootmgr -v shows.
I that state is not good (BootCurrent is set, but no entry to match)
then that's firmware bug (IMHO). If current entry is present then we
likely do have a parsing bug.
Either way the full log with efibootmgr -v dump in the logs will shed
light on what to do next.
** Changed in: curtin (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1894217
Title:
2.8.2 deploy and commission fails corrupted bootorder variable
detected
To manage notifications about this bug go to:
https://bugs.launchpad.net/maas/+bug/1894217/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
