Hi,

I know this bug was gone for a while, but now there are my findings
which may be a regression:

Test environment:
MAAS version: 2.5.0 (7442-gdf68e30a5-0ubuntu1~18.04.1)

1. Dell G3 3590 laptop with secure boot enabled

Deploying 18.04 from MAAS => Got the same error as bug described.
Deploying 19.10 from MAAS => Got the same error as bug described.

2. Shuttle Inc. DH270 with secure boot enabled

Deploying 18.04 from MAAS => Got the same error as bug described.
Deploying 19.10 from MAAS => Got the same error as bug described.

>From screenshot I attached, it apparently said the machine had enabled
secure boot but it still show shim's message.

Another phenomenon was doing grub chainload from local disk, the grub
provided by maas will find grubx64.efi from /efi/boot instead of
/efi/ubuntu/ and it reported *no found" from that path because
grubx64.efi actually didn't exist under /efi/boot/. I'm not sure if this
behaviour is expected or not.

Any comment?

** Attachment added: "maas.jpg"
   
https://bugs.launchpad.net/maas/+bug/1711203/+attachment/5309736/+files/maas.jpg

-- 
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