The MAAS environment I've been using to reproduce this is virtual. I
have MAAS running in an LXD container connected to an LXD Pod. To
recreate this environment you'll have to install MAAS 2.8, python-pylxd
from github(if using the Debian packages), and apply this[1] patch to
reenable secure boot. After MAAS is setup you'll need to configure LXD
to accept remote connections to be able to add it as a MAAS Pod.

This bug should be reproducible using LXD

1. Download GRUB and the shim. MAAS gets both from Bionic, you can download 
them direct here[1]
2. Setup a TFTP server to provide them
3. Add grub.cfg from MAAS[3]
4. Setup DHCP - Example dhcpd.conf from MAAS[4]
5. Create LXD VM
6. Modify LXD VM to boot from over the network
7. See boot failure


You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

  Chainbooting from grub over the network to local shim breaks chain of

To manage notifications about this bug go to:

ubuntu-bugs mailing list

Reply via email to