curtin-dev team mailing list archive

[Andrew Cloke <1789650@xxxxxxxxxxxxxxxxxx>]

Adding "MAAS" as an impacted project, as it appears there are questions
about the curtin preseed that MAAS uses.

Could someone from the MAAS team help to answer Ryan's question?

** Also affects: maas
   Importance: Undecided
       Status: New

-- 
You received this bug notification because you are a member of curtin
developers, which is subscribed to curtin.
https://bugs.launchpad.net/bugs/1789650

Title:
  Servers set to boot from disk after MAAS installation

Status in curtin:
  Incomplete
Status in MAAS:
  New

Bug description:
  This bug appears to be a regression of bug #1311827 and/or bug
  #1642298, but it seems to affect only some servers. Upon deployment
  via MAAS, the server is set to boot from the "ubuntu" EFI boot order
  entry -- that is, it boots directly from disk, bypassing the PXE-boot
  option. Immediately after deployment, the boot order looks like this:

  $ sudo efibootmgr
  BootCurrent: 0000
  BootOrder: 0000,0002,0001,0003,0004,0005,0006,0007,0008
  Boot0000* ubuntu
  Boot0001* Hard Disk 0
  Boot0002* PXE Network
  Boot0003  Enter Setup
  Boot0004  Boot Devices
  Boot0005  Boot Manager
  Boot0006  Setup
  Boot0007  Diagnostics
  Boot0008  Firmware Log

  This bug is affecting two Lenovo servers (drapion and jolteon), when
  deployed with either Ubuntu 18.04 or 16.04. These servers seemed OK in
  tests in late April. Other servers we've recently tested are NOT
  affected. Changes to the boot order after installation do "stick," and
  it's possible to entirely delete the "ubuntu" entry without it being
  re-created, so I doubt if the firmware is creating the entry or making
  it the default; it appears that the bug is somewhere in Ubuntu. I'm
  reporting this against curtin, but it could be GRUB or something else
  is the true cause.

To manage notifications about this bug go to:
https://bugs.launchpad.net/curtin/+bug/1789650/+subscriptions