Ok, so I've tested the workaround in a supermicro system provided by the
cert team, and this is my evaluation:
1. Without the workaround on #36, the machine fails to deploy (e.g.
Using the shim fails and the machine powersoff)
2. With the work around on #36, the machine deploys successfully.
I'm making this change in MAAS as a working work around.
** Changed in: maas
Status: Invalid => Triaged
** Changed in: maas
Importance: Critical => High
** Changed in: maas
Assignee: (unassigned) => Andres Rodriguez (andreserl)
--
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
