[Bug 1229458] Please test proposed package

[Andy Whitcroft]

Hello Steve, or anyone else affected,

Accepted grub2-signed into xenial-proposed. The package will build now
and be available at
https://launchpad.net/ubuntu/+source/grub2-signed/1.66.4 in a few hours,
and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
enable and use -proposed.  Your feedback will aid us getting this update
out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, and change the tag
from verification-needed to verification-done. If it does not fix the
bug for you, please add a comment stating that, and change the tag to
verification-failed.  In either case, details of your testing will help
us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to grub2 in Ubuntu.
https://bugs.launchpad.net/bugs/1229458

Title:
  grubnetx64.efi tftp client does not work over ipv6

Status in MAAS:
  Fix Released
Status in grub2 package in Ubuntu:
  Fix Released
Status in grub2-signed package in Ubuntu:
  Fix Released
Status in grub2 source package in Xenial:
  Fix Committed
Status in grub2-signed source package in Xenial:
  Fix Committed

Bug description:
  [Impact]
  Trying to PXE boot (with UEFI) over IPv6 with grub. This is especially relevant for MAAS users in IPv6 setups.

  [Test cases]

  [IPv6 PXE boot]
  0) Setup PXE boot infrastructure (https://wiki.ubuntu.com/UEFI/SecureBoot-PXE-IPv6, also https://github.com/openSUSE/kiwi/wiki/Setup-PXE-boot-with-EFI-Using-GRUB2 contains relevant information)
  1) Attempt to PXE boot (with UEFI) over IPv6 a system.

  [IPv4 PXE boot]
  0) Setup PXE boot infrastructure;
  Required DHCP config:
   - filename should specify the path to the efi binary to use to boot, or to pxelinux in a non-EFI case.
   - next-server should be set to the TFTP server.
  1) Attempt to PXE boot (with and without UEFI) with IPv4.

  [IPv4 PXE boot with HTTPClient]
  0) Setup PXE boot infrastructure;
  Required DHCP config:
   - set vencor class to HTTPClient.
   - configure filename to be the url to the pxelinux (non-UEFI) or EFI binary (UEFI)
   - next-server should be set to the TFTP server.
  1) Attempt to PXE boot (with and without UEFI) with IPv4.

  [MaaS deployment in IPv4 network]
  1) deploy a system using MaaS in an IPv4-only network.

  [MaaS deployment in IPv6 network]
  1) deploy a system using MaaS in an IPv6-only network.

  [MaaS deployment in a mixed network]
  1) deploy a system using MaaS on a network with both IPv4 and IPv6.

  Testers can use grubnetx64.efi.signed from
  http://archive.ubuntu.com/ubuntu/dists/xenial-
  proposed/main/uefi/grub2-amd64/current/ once the package is available
  in proposed.

  [Regression potential]
  Possible regressions include any issues in routing IPv4 or IPv6 and/or retrieving files over PXE/tftp via grub. Ping is a good way to validate that routing is being done correctly, so is actually booting using the build grubnetx64.efi.

  ---

  Testing using the pre-built grubnetx64.efi, I am not able to use the
  tftp client support within grub2 to load configs (/kernels/initrds)
  over the network.  This works fine if using IPv4.

  grubnetx64.efi is being loaded over the network (via shim no less), so
  the firmware's network stack is definitely up and working.  But when
  grub tries to load grub.cfg via the default path, it fails with:

    error: couldn't send network packet.

  This message is repeated, approximately once every three seconds.  It
  looks to be an infinite loop; at least, the message is repeated more
  than 100 times.  But sometimes, when I've not been paying close
  attention to the boot, I get a grub shell instead.  In that case, the
  grub shell shows:

  grub> echo $root
  tftp,0.5.0.24
  grub> set
  [...]
  net_default_server=
  net_efinet2_boot_file=8:23f::2]/bootx64.efi
  net_efinet2_ip=0.0.0.0
  net_efinet2_mac=02:3f:00:00:00:00
  [...]
  prefix=(tftp,0.5.0.24)/grub
  pxe_default_server=
  root=tftp,0.5.0.24
  [...]
  grub>

  The actual server IP is 2001:1938:23f::2.

  I've booted a locally-generated (self-signed) grubnetx64.efi with
  grub-bootstrap.cfg modified to call 'set' first, and I get identical
  output for all of the network-related variables.

To manage notifications about this bug go to:
https://bugs.launchpad.net/maas/+bug/1229458/+subscriptions