[Bug 1510120] Re: UEFI deployment broken in MAAS 1.9

[Blake Rouse]

** Changed in: maas
       Status: Triaged => In Progress

** No longer affects: grub2-signed (Ubuntu)

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to grub2-signed in Ubuntu.
https://bugs.launchpad.net/bugs/1510120

Title:
  UEFI deployment broken in MAAS 1.9

Status in MAAS:
  In Progress

Bug description:
  UEFI-mode deployment seems to be broken in MAAS 1.9. Enlistment and
  commissioning work fine, as does most of deployment; however, there
  seems to be a problem with the GRUB configuration. Instead of the
  normal boot at the end of deployment, I get a GRUB menu with one
  option. Selecting that fails and, after a prompt to press a key,
  brings up the same menu. The GRUB on the hard disk seems to work,
  though; I'm able to boot to it via a boot to rEFInd on a USB drive and
  boot the system. Thus, it seems to be the GRUB being sent via PXE from
  the MAAS server that's unable to redirect to GRUB on the hard disk (or
  use the disk-based GRUB files).

  Here's the version information:

  $ dpkg -l '*maas*'|cat
  Desired=Unknown/Install/Remove/Purge/Hold
  | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
  |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
  ||/ Name                                                  Version                                             Architecture Description
  +++-=====================================================-===================================================-============-===============================================================================
  ii  maas                                                  1.9.0~alpha5+bzr4383-0ubuntu1~trusty1               all          MAAS server all-in-one metapackage
  ii  maas-cert-server                                      0.2.6-0~34~ubuntu14.04.1                            all          Ubuntu certification support files for MAAS server
  ii  maas-cli                                              1.9.0~alpha5+bzr4383-0ubuntu1~trusty1               all          MAAS command line API tool
  ii  maas-cluster-controller                               1.9.0~alpha5+bzr4383-0ubuntu1~trusty1               all          MAAS server cluster controller
  ii  maas-common                                           1.9.0~alpha5+bzr4383-0ubuntu1~trusty1               all          MAAS server common files
  ii  maas-dhcp                                             1.9.0~alpha5+bzr4383-0ubuntu1~trusty1               all          MAAS DHCP server
  ii  maas-dns                                              1.9.0~alpha5+bzr4383-0ubuntu1~trusty1               all          MAAS DNS server
  ii  maas-proxy                                            1.9.0~alpha5+bzr4383-0ubuntu1~trusty1               all          MAAS Caching Proxy
  ii  maas-region-controller                                1.9.0~alpha5+bzr4383-0ubuntu1~trusty1               all          MAAS server complete region controller
  ii  maas-region-controller-min                            1.9.0~alpha5+bzr4383-0ubuntu1~trusty1               all          MAAS Server minimum region controller
  ii  python-django-maas                                    1.9.0~alpha5+bzr4383-0ubuntu1~trusty1               all          MAAS server Django web framework
  ii  python-maas-client                                    1.9.0~alpha5+bzr4383-0ubuntu1~trusty1               all          MAAS python API client
  ii  python-maas-provisioningserver                        1.9.0~alpha5+bzr4383-0ubuntu1~trusty1               all          MAAS server provisioning libraries

  I'm attaching the /var/log/maas directory tree. Note that I've
  reconfigured my two UEFI-based nodes to boot in BIOS/CSM/legacy mode
  to work around this issue for the time being.

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