Comment 6 for bug 1767584

Revision history for this message
Ryan Harper (raharper) wrote :

I believe this is an issue with curtin's use of efibootmgr. We're calling efibootmgr with -o, --bootorder which the manpage says, each entry must exist:

-o | --bootorder XXXX,YYYY,ZZZZ
Explicitly set BootOrder (hex). Any value from 0 to FFFF is accepted so long as it corresponds to an existing Boot#### variable, and zero padding is not required.

Curtin should adjust the order value and drop any entry reference to a value that's not found in the entry list.