I'm attaching the contents of the /var/lib/maas/boot- resources/snapshot-20160426-183112 directory on the MAAS server (minus the ubuntu and custom directories, which contain OS images and are therefore huge). This tarball includes the shim and GRUB images used in this process. I'm also including an excerpt from the clusterd.log file from the MAAS server, which shows the TFTP requests.
You're correct that the system boots in two stages: When a node PXE- boots, it requests a boot loader from the MAAS server, which delivers an image that then kicks the boot process to the local disk. Thus, the boot process should be: PXE request -> TFTP-delivered Shim -> TFTP-delivered GRUB -> local Shim -> local GRUB -> local kernel At least, that's my understanding; I'm not involved in MAAS development in any significant way, so I could be misunderstanding something. The symptoms look like the handoff from the TFTP-delivered GRUB to the local Shim is failing when Secure Boot is active. The file is definitely present because it DOES work when Secure Boot is inactive. ** Attachment added: "Contents of MAAS directory holding shim, GRUB, etc." https://bugs.launchpad.net/ubuntu/+source/shim/+bug/1578837/+attachment/4657251/+files/snapshot-20160426-183112.tgz -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1578837 Title: Secure Boot failure on Lenovo x3550 M5 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shim/+bug/1578837/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
