yahoo-eng-team team mailing list archive

[Jeff Lane <jeffrey.lane@xxxxxxxxxxxxx>]

Gah! thanks, I didn't even notice that before... thanks for pointing it
out.

** Also affects: maas-cert-server
   Importance: Undecided
       Status: New

** Changed in: maas-cert-server
       Status: New => Confirmed

** Changed in: maas-cert-server
   Importance: Undecided => Critical

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to cloud-init.
https://bugs.launchpad.net/bugs/1807030

Title:
  Deployment fails due to missing EFI directory on system with no EFI
  support

Status in cloud-init:
  Invalid
Status in curtin:
  Invalid
Status in MAAS:
  Invalid
Status in maas-cert-server:
  Confirmed

Bug description:
  Attempting to deploy various versions of Ubuntu via MAAS 2.4.2
  (7034-g2f5deb8b8-0ubuntu1). I've tried 16.04.5 and 18.04.1 and end up
  with messages in the logs like such:


  Looking in the system settings, this system does not use EFI at all.
  It is purely BIOS mode, yet the installer is complaining about a
  missing efi directory when it fails.

  The machine is successfully commissioned, and commissioning does not
  detect EFI and thus does not create a /boot/efi partition as it is not
  necessary.  Watching the node boot via console, it clearly is doing a
  BIOS mode PXE boot from the NICs, it is not loading an EFI environment
  first.

  
  A search and skimming of the manuals for this model (ProLiant SL230s) shows that it has no EFI options available as well: 
  https://support.hpe.com/hpsc/doc/public/display?docId=c03239129
  https://support.hpe.com/hpsc/doc/public/display?docId=emr_na-c03239183

  Installation finished. No error reported.


  Running command ['udevadm', 'settle'] with allowed return codes [0]
  (capture=False)

  Running command ['umount', '/tmp/tmpmg3cwxp7/target/sys'] with allowed
  return codes [0] (capture=False)

  Running command ['umount', '/tmp/tmpmg3cwxp7/target/proc'] with
  allowed return codes [0] (capture=False)

  Running command ['umount', '/tmp/tmpmg3cwxp7/target/dev'] with allowed
  return codes [0] (capture=False)

  finish: cmd-install/stage-curthooks/builtin/cmd-curthooks: SUCCESS:
  curtin command curthooks

  start: cmd-install/stage-hook/builtin/cmd-hook: curtin command hook

  Finalizing /tmp/tmpmg3cwxp7/target

  finish: cmd-install/stage-hook/builtin/cmd-hook: SUCCESS: curtin
  command hook

  curtin: Installation failed with exception: Unexpected error while
  running command.

  Command: ['grep', 'efi', '/proc/mounts']

  Exit code: 1

  Reason: -

  Stdout: ''

  Stderr: ''

  A full paste of the install lot from the MAAS web ui is here:
  https://pastebin.canonical.com/p/6SCncBtHGd/

  And the node's config data from MAAS can be found here:
  https://pastebin.canonical.com/p/dbV7PTVnYw/

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1807030/+subscriptions