Ubuntu
shim package

  1. Bionic (18.04)
  2. Bug #1711203
  3. Comment #59

Comment 59 for bug 1711203

Revision history for this message
Andres Rodriguez (andreserl) wrote :

FWIW, I did a bit of extra testing. I killed maas' rackd (which provides PXE). Rebooted the machine and I saw:

1. It attempted to PXE boot multiple times (like a lot)
2. It eventually gave up and booted from disk

So it successfully booted into the deployed OS.

I noticed that the curtin installation reported the boot order, and seems that (1) above was caused because of the following:

BootCurrent: 0006
Timeout: 1 seconds
BootOrder: 0006,0000,0004,0003,0008,0007,0005,0009,000A
Boot0000* ubuntu
Boot0003* UEFI: Intel(R) I350 Gigabit Network Connection
Boot0004* UEFI: IP4 Intel(R) I350 Gigabit Network Connection
Boot0005* UEFI: Intel(R) I350 Gigabit Network Connection
Boot0006* UEFI: IP4 Intel(R) I350 Gigabit Network Connection
Boot0007* UEFI: Intel(R) 82599 10 Gigabit Dual Port Network Connection
Boot0008* UEFI: IP4 Intel(R) 82599 10 Gigabit Dual Port Network Connection
Boot0009* UEFI: Intel(R) 82599 10 Gigabit Dual Port Network Connection
Boot000A* UEFI: IP4 Intel(R) 82599 10 Gigabit Dual Port Network Connection