Comment 20 for bug 1894217

@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.