I'm at a loss to explain that. This works quite well in my netboot
testing when I remove MAAS from the equation. You *are* meant to be able
to chainload grub from another grub; and the reason why grub can't
chainload shim is that you then get the wrong set of shim protocols to
properly validate the next binary. This will need more testing; I will
need to know what hardware this is and what exactly is the content of
the grub configs.

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

Title:
  Deployments fail when Secure Boot enabled

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to