No one in this thread has answered how MAAS or curtin knows that it should install the -signed version of linux-image.
Once that knowledge is passed on, we can work out if curtin can detect that or if maas can and specify which kernel package to use. On Thu, Nov 16, 2017 at 3:25 PM, Steve Langasek < steve.langa...@canonical.com> wrote: > If maas+curtin are not installing the signed variant of the linux-image > package on UEFI systems, this is not invalid for maas+curtin - when we > rev the grub secureboot policy (ETA January), these systems will be > unbootable BY DESIGN. Regardless of whether this configuration has > tickled a regression in grub, this MUST be fixed. > > ** Changed in: maas > Status: Invalid => Confirmed > > ** Changed in: grub2 (Ubuntu) > Status: Confirmed => Won't Fix > > -- > You received this bug notification because you are subscribed to curtin. > Matching subscriptions: curtin-bugs-all > 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 > -- 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
