Comment 4 for bug 1680917

Thanks for the prompt action Andres!

After a bit more debugging, here is the root cause:

Despite the fact that this is a UEFI system, we do not install a signed linux kernel.
Seems that some EFI implementations are more pedantic than others, thus it affects Intel NUCs but not other systems.

Indeed, going through the repro steps:

1. Install on the node (Intel NUC) Ubuntu 16.04 (default flat disk layout, default network config)
2. SSH into the deployed node.
3. (this is the workaround)
sudo apt-get install linux-signed-generic
sudo dpkg-reconfigure grub-efi-amd64-signed
4. On the MAAS server, terminate all MAAS services.
5. On the deployed node, do a reboot.

Observed behavior: the machine properly boots from its disk, as expected.

From my side I am happy with the workaround for the time being, but it would be great if the fix could land with 2.2.0rc2