We've seen similar reports for this issue during the past weeks. Every time, the BootCurrent entry has no associated BootXXXX entry. I looked in the UEFI spec and it's still unclear to me if this is a stretch or a broken implementation.
That said, based on the number of reports, I believe we should still do something about it. As far as subiquity is concerned, I don't think trying to set the install media as the first boot entry makes sense so I've disabled the behavior in https://github.com/canonical/subiquity/pull/1671
I'd still argue that curtin should do the right think on "broken" UEFI implementations if we can.
Hello Taihsiang,
We've seen similar reports for this issue during the past weeks. Every time, the BootCurrent entry has no associated BootXXXX entry. I looked in the UEFI spec and it's still unclear to me if this is a stretch or a broken implementation.
That said, based on the number of reports, I believe we should still do something about it. As far as subiquity is concerned, I don't think trying to set the install media as the first boot entry makes sense so I've disabled the behavior in https:/ /github. com/canonical/ subiquity/ pull/1671
I'd still argue that curtin should do the right think on "broken" UEFI implementations if we can.
Thanks,
Olivier